If that's reasonable, and someone from @conda-forge/root can create the maintenance branch, I am happy to cherry-pick those migrations into a new branch to build a new 6.32.0 package that includes them. If instead its actually cleaner/faster/less work to just start the migration to 6.32.2, I'm happy to wait for that to propagate.
Comment:
Currently conda-forge-pinning pins downstream projects to root_base 6.32.0, while the latest release here is (ATOW) 6.32.2.
Rather than migrating to 6.32.2 (https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/6127) it might be faster to backport the cfitsio441 (#263) and numpy2 (#265) migrations to a maintenance branch for 6.32.0.
If that's reasonable, and someone from @conda-forge/root can create the maintenance branch, I am happy to cherry-pick those migrations into a new branch to build a new 6.32.0 package that includes them. If instead its actually cleaner/faster/less work to just start the migration to 6.32.2, I'm happy to wait for that to propagate.
Thanks.