Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Anitya should report every found version, not only latest #774

Closed
Zlopez opened this issue Apr 18, 2019 · 2 comments · Fixed by #971
Closed

Anitya should report every found version, not only latest #774

Zlopez opened this issue Apr 18, 2019 · 2 comments · Fixed by #971
Assignees
Labels
groomed Medium Priority This ticket has a medium priority type.feature New feature
Milestone

Comments

@Zlopez
Copy link
Contributor

Zlopez commented Apr 18, 2019

Anitya is currently reporting only newest version. This should be changed to allow sending more than one version in the anitya.project.version.update topic.

For this to work we need to do some changes:

  1. Upstream version needs to be changed to array in anitya.project.version.update topic
  2. There also needs to be change in the-new-hotness to be able to work with this
@Zlopez Zlopez added type.feature New feature Medium Priority This ticket has a medium priority labels Apr 18, 2019
@voxik
Copy link
Contributor

voxik commented Apr 18, 2019

Just FTR, this would be useful for Fedora modularity, which allows to have supported multiple stable streams for package, e.g. Ruby 2.4, 2.5 and 2.6 at the same time.

@Zlopez
Copy link
Contributor Author

Zlopez commented Apr 18, 2019

@voxik It shouldn't be a problem to just add Fedora Modules distribution to Anitya, so we map packages to modules.
But to make this work properly in the-new-hotness could prove difficult. I will create a issue on the-new-hotness for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
groomed Medium Priority This ticket has a medium priority type.feature New feature
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants