Fix package availability queries to use the API#634
Merged
marcelotrevisani merged 2 commits intoconda:mainfrom Jan 17, 2026
Merged
Fix package availability queries to use the API#634marcelotrevisani merged 2 commits intoconda:mainfrom
marcelotrevisani merged 2 commits intoconda:mainfrom
Conversation
Fix anaconda.org package availability queries to use API URLs rather than webpages. The latter have recently started returning 200 status code even when the text indicates a 404 error, and using the API is more correct anyway. Technically, we could also switch to HEAD requests, but I'm not sure if that wouldn't break some custom URLs. Signed-off-by: Michał Górny <mgorny@gentoo.org>
This was referenced Jan 14, 2026
marcelotrevisani
approved these changes
Jan 16, 2026
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
2 participants
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.
Description
Fix anaconda.org package availability queries to use API URLs rather than webpages. The latter have recently started returning 200 status code even when the text indicates a 404 error, and using the API is more correct anyway. Technically, we could also switch to HEAD requests, but I'm not sure if that wouldn't break some custom URLs.