Fix #20066: Disable Anitya version checks for aggregate and link packages - #20266
Open
Akarshkushwaha wants to merge 1 commit into
Open
Fix #20066: Disable Anitya version checks for aggregate and link packages#20266Akarshkushwaha wants to merge 1 commit into
Akarshkushwaha wants to merge 1 commit into
Conversation
Akarshkushwaha
force-pushed
the
fix-anitya-status-aggregates-20066
branch
2 times, most recently
from
September 6, 2026 05:46
b95231d to
dac21da
Compare
Akarshkushwaha
force-pushed
the
fix-anitya-status-aggregates-20066
branch
from
September 6, 2026 06:36
dac21da to
11184d3
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #20066
The new Anitya version check feature is currently trying to fetch upstream versions for aggregate and link packages. Since these packages just pull sources from elsewhere and aren't standalone upstream projects, this leads to an incorrect/red status in the WebUI.
As suggested in the issue, this PR explicitly disables the Anitya version sync for any package that is a
linkoraggregate.I've also included a quick data migration to sweep up any incorrectly synced upstream versions for these packages so that the bad frontend status clears up immediately upon deployment.