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

Intermediate versions are skipped while update checking #1273

Closed
dfateyev opened this issue Jan 20, 2022 · 1 comment · Fixed by #1274
Closed

Intermediate versions are skipped while update checking #1273

dfateyev opened this issue Jan 20, 2022 · 1 comment · Fixed by #1274
Labels
easyfix Medium Priority This ticket has a medium priority type.feature New feature

Comments

@dfateyev
Copy link

The issue that some upstream intermediate versions are now skipped from new versions reporting — when a newer version presents in the version list (e.g. a pre-release one which can look "newer" than stable ones.)

Briefly discussed it with @Zlopez, seems we need remove deprecated limitations on intermediate version reporting.

@Zlopez Zlopez added easyfix type.feature New feature Medium Priority This ticket has a medium priority labels Jan 20, 2022
@Zlopez
Copy link
Contributor

Zlopez commented Jan 20, 2022

The code in question could be found here https://github.com/fedora-infra/anitya/blob/master/anitya/lib/utilities.py#L143

After this change Anitya will send a fedora message every time it finds any new version (versions) not only latest one according to current sort method.

Zlopez added a commit that referenced this issue Jan 20, 2022
Till now we only sent message when the new version was considered
newest. With this commit the logic is changing and we will send the
update message with every retrieved version.

Fixes #1273

Signed-off-by: Michal Konečný <[email protected]>
Zlopez added a commit that referenced this issue Jan 20, 2022
Till now we only sent message when the new version was considered
newest. With this commit the logic is changing and we will send the
update message with every retrieved version.

Fixes #1273

Signed-off-by: Michal Konečný <[email protected]>
Zlopez added a commit that referenced this issue Jan 20, 2022
Till now we only sent message when the new version was considered
newest. With this commit the logic is changing and we will send the
update message with every retrieved version.

Fixes #1273

Signed-off-by: Michal Konečný <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
easyfix 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