Repository navigation
Conversation
Some packages skip x.y.0 on conda-forge (e.g. netcdf4 1.7 starts at 1.7.1), so the policy never considered those minor versions released. Co-authored-by: Claude <noreply@anthropic.com>
5 tasks done
Author
This branch has not been deployed
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
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.
Use the first release of each minor version for the policy instead of requiring a
x.y.0release. Some packages skipx.y.0on conda-forge, e.g. netcdf4 1.7 starts at 1.7.1, so the policy never considered 1.7 released and still required 1.6.is_suitable_releasenow only excludes pre-releases instead of everything butx.y.0x.y.0does not exist #25, which fixed the lookup of the required version but not the policy version🤖 Generated with Claude Code