How to run Python 3.14 migration

[marcelotduarte]

Comment:

@ocefpaf
When I created freeze-core-feedstock, the Python 3.14 migration ran a few hours later. It hasn't run on this repository yet. Is there a way to run the Python 3.14 migration via conda-forge-admin?

[marcelotduarte]

cc @conda-forge/help-python

[ocefpaf]

No idea. Maybe the bot didn't pick it up yet. (It could be that the package dependencies are not yet solvable for py314).

Pinging @conda-forge/core

[h-vetinari]

It doesn't show up anywhere in the status page yet, which means it hasn't made it through the bowels of https://github.com/regro/cf-scripts yet (i.e. integrated into the graph which the migrators then work through). The actions seem to be running normally though, so no idea why it hasn't shown up yet.

[marcelotduarte]

It has no dependencies other than setuptools to build.
Could the cause be that the skip rule is tricking the bot?
https://github.com/conda-forge/python-msilib-feedstock/blob/main/recipe/recipe.yaml#L18
skip: not (win and match(python, ">=3.13"))

[h-vetinari]

It shouldn't, but anything in v1-land is potentially at risk to run into untested codepaths or assumptions. 🤷

[marcelotduarte]

@h-vetinari Even regro-cf-autotick-bot isn't working for this repository. Two days ago, I released a new version of freeze-core, and about an hour and forty minutes later, the bot made the update request. Shortly after, I released a version of python-msilib and waited about 6 hours. Since the bot didn't run, I did the update manually and took the opportunity to release a version for Python 3.10+ (I only need 3.13+) to see if the migrator would run for 3.14, but nothing.
What do you suggest I do?

[h-vetinari]

Open an issue in https://github.com/regro/cf-scripts :)