Github labels for upgrade dealbreaker regressions

Can we have a Github label (e.g. regression-25.11) for issues that are likely dealbreakers for people upgrading to a specific release, so that people can more easily check if the upgrade will break their system?

For example for the 25.11 release, I found the following regressions that would likely break my workflow and waste time:

Future release upgrade instructions could then also recommend to check that label before upgrading.

Note we already have label 0.kind: regression but that does not allow users to filter for the release they are looking to upgrade to.

3 Likes