Package badges do not exclude broken releases

[tpdownes]

Checklist

• I added a descriptive title
• I searched open reports and couldn't find a duplicate

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.

• https://anaconda.org/conda-forge/protobuf/files?version=21.2
• google-cloud-life-sciences v0.9.2 conda-forge/google-cloud-life-sciences-feedstock#15

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

active environment : default
    active env location : /Users/tpdownes/local/miniconda3/envs/default
            shell level : 1
       user config file : /Users/tpdownes/.condarc
 populated config files : /Users/tpdownes/local/miniconda3/.condarc
                          /Users/tpdownes/.condarc
          conda version : 23.1.0
    conda-build version : not installed
         python version : 3.10.9.final.0
       virtual packages : __archspec=1=x86_64
                          __osx=13.2.1=0
                          __unix=0=0
       base environment : /Users/tpdownes/local/miniconda3  (writable)
      conda av data dir : /Users/tpdownes/local/miniconda3/etc/conda
  conda av metadata url : None
           channel URLs : https://conda.anaconda.org/conda-forge/osx-64
                          https://conda.anaconda.org/conda-forge/noarch
          package cache : /Users/tpdownes/local/miniconda3/pkgs
                          /Users/tpdownes/.conda/pkgs
       envs directories : /Users/tpdownes/local/miniconda3/envs
                          /Users/tpdownes/.conda/envs
               platform : osx-64
             user-agent : conda/23.1.0 requests/2.28.2 CPython/3.10.9 Darwin/22.3.0 OSX/13.2.1
                UID:GID : 828971:89939
             netrc file : None
           offline mode : False

Conda Config

==> /Users/tpdownes/local/miniconda3/.condarc <==
channels: []

==> /Users/tpdownes/.condarc <==
auto_activate_base: False
changeps1: False
create_default_packages:
  - coreutils
default_threads: 5
channel_priority: strict
channels:
  - conda-forge

Conda list

No response

Additional Context

No response

[tpdownes]

Was advised by conda-forge/protobuf-feedstock#181 to file an issue in this repo.

[github-actions]

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:

1. Verify that you can still reproduce the issue at hand
2. Comment that the issue is still reproducible and include:
   - What OS and version you reproduced the issue on
   - What steps you followed to reproduce the issue

NOTE: If this issue was closed prematurely, please leave a comment.

Thanks!

[jakirkham]

This is still an issue

[jakirkham]

@jezdez is this something we could look into?