Conda-forge.github.io: Autogenerate a new release PR by merging the dev/rc branch if it exists?

[leofang]

Currently,

• The bot is good at discovering new releases and generating a PR for it
• According to CFEP-05 there can be a dev or rc branch publishing pre-releases (although the bot is currently not discovering new pre-release versions for us)

I am not suggesting to fix item 2, but am simply wondering if it is possible for the bot to take advantage of the fact that a dev/rc branch exists. Specifically, say a package with x.y.z.rc1 is released from the rc branch, when the bot sends a PR targeting the master branch for the official release x.y.z, it should also merge from the rc branch. The reason is that at this point some necessary changes in the recipe are likely already performed by package maintainers in the rc branch, and it'd be nice to simply copy them over to master instead of having maintainers touch the bot's PR manually for such updates. Just a thought.

[CJ-Wright]

Are you interested in putting up a PR into the bot for this? This use case seems a bit niche to me, since I think number of pkgs shipping rc branches is small. That being said, if you need that niche filled, I'd be happy to review this. Note that this will need to handle the correct rc -> branch mapping and updates to things beyond the meta.yaml (eg build.sh)

[leofang]

Thanks, CJ. I don't even know where the bot code is 😂 If you could give me a few pointers I can take a quick look and evaluate the dev time needed, thanks.

[beckermr]

regro/cf-scripts

[leofang]

So is this the main file that I should look at?
https://github.com/regro/cf-scripts/blob/master/conda_forge_tick/update_upstream_versions.py

[beckermr]

That file is used for getting upstream versions. For the code that makes the PR, you want the class in the migrators submodule. We should move this convo to the cf-scripts repo.