-
Notifications
You must be signed in to change notification settings - Fork 15
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
Package badges do not exclude broken releases #737
Comments
Was advised by conda-forge/protobuf-feedstock#181 to file an issue in this repo. |
Hi there, thank you for your contribution! This issue has been automatically marked as stale because it has not had recent activity. It will be closed automatically if no further activity occurs. If you would like this issue to remain open please:
NOTE: If this issue was closed prematurely, please leave a comment. Thanks! |
This is still an issue |
@jezdez is this something we could look into? |
Checklist
What happened?
Recently, the Google protobuf repository changed its versioning scheme such that the repo is tagged with, e.g. 22.2, but the specific language implementations in the repo may have a major version prepended. e.g. the Python release is 4.22.2.
During this transition conda-forge released a version 21.2 of the package. This problem was reported and the packages marked broken. Nevertheless, badges report the 21.2 release as the highest available on conda-forge. It doesn't seem right to include broken packages in this calculation.
I understand that the upstream badge reports 22.2 and that may not have a good, generalizable solution. I'm focusing on the channel badge.
Conda Info
Conda Config
Conda list
No response
Additional Context
No response
The text was updated successfully, but these errors were encountered: