How to debug missing PR's to branches (different version releases)

[ZzEeKkAa]

llvm-spirv-feedstock does not have PRs to newer versions of llvm-spirv on the branches different from main:
There is branch 15.X branch with version=15.0.0. However there is a new release v15.0.1: https://github.com/KhronosGroup/SPIRV-LLVM-Translator/releases/tag/v15.0.1 . There is also an automated PR to main for 18.0.0 -> 18.0.1: conda-forge/llvm-spirv-feedstock#26

Issue is mentioned here: conda-forge/llvm-spirv-feedstock#23

[beckermr]

The bot won't make these PRs. Making it do that is super hard for a few reasons.

• We do not have conventions for how people label release branches.
• The internal structure of the bot has too many assumptions to support that easily right now.

We are unlikely to be able to enable this soon.

[ZzEeKkAa]

@beckermr thank you for the fast reply! SPIRV-LLVM-Translator going to create patch releases for at least 4 different versions every month..
Are there any open discussions how to come to this point.

In a meantime, it will be handy to have a comment here, so that it is obvious that bot does not open automatic PRs for such branches.

[beckermr]

We do not have any open discussions. A path forward has to:

1. Specify how we infer that a branch on a feedstock gets version updates and what constraints those have. We could only support variants of branch names that match this regex (v)(([0-9]+\.)*)x (i.e., v5.6.x, 5.6.x, 5.x, etc.)
2. Figure out how to migrate the bot's version information schemas to support more than one branch
3. Update the bot's version search code to search for branches as well

This is all a big lift in terms of dev.

[ZzEeKkAa]

Thank you!

Does it mean if somebody will implement it that it looks into (v)(([0-9]+\.)*)x branches and opens PRs for them keeping the same prefix, the PR will be merged without redefining requirements.

If I would have time I can try to implement it and open a PR.

[beckermr]

It's a bit more complicated than that and will require a lot of work.