Update pin for cfitsio 4.6.2

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update the pin for cfitsio. The current pinned version is 4.3.1, the latest available version is 4.6.2 and the max pin pattern is x.x.x. This migration will impact 30 feedstocks.

Checklist:

• The new version is a stable supported pin.
• I checked that the ABI changed from 4.3.1 to 4.6.2.

**Please note that if you close this PR we presume that the new pin has been rejected.

@conda-forge-admin please ping cfitsio

_{This PR was generated by https://github.com/regro/cf-scripts/actions/runs/14234498350 - please use this URL for debugging.}

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/cfitsio and so here I am doing that.

[conda-forge-admin]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[pkgw]

@conda-forge/conda-forge-pinning There's already a migration to 4.6.0 partially underway, but we should switch over to this version because 4.6.0 built its pkg-config file in a buggy way. Is that just a matter of deleting the migration file for the 4.6.0 here, or is there something fancier that would need to be done?

[h-vetinari]

The two migrations can run independently from each other - actually I see that there are also open migrations for cfitsio 4.4.1 & 4.5.0.

Ideally, you'd pick one of the open migrations, go through the list of open PRs, try to push them over the finish line where possible, and then open a PR to close the migration, noting which stragglers are intentionally ignored. Here's an example of how I'd tackle something like that.

Deleting the old migrations should only happen when we actually bump the global pinning to at least that level (because otherwise already-migrated feedstocks would fall down to a previous version upon rerendering).

For example, we may be happy to bump to 4.5.0 in the pinning (simultaneously with closing the 4.4.1 & 4.5.0 migrators), and then declare 4.6.0 as superseded by 4.7.0, but delete the 4.6 migrator only when we bump the pinning to 4.7 (this is just a suggestion based on a superficial read of the situation, feel free to pick different waypoints).

[pkgw]

In that case, I think the best approach is to just close out all of the currently-open migrations and supersede them with this new one.

Of the open pull requests for the older two migrations, they're basically all about unresponsive maintainers. There's no point merging these if they're about to be followed by yet more PRs.

For the most recent migration, some would probably be dealt with before long, but once again, we might as well just close them. And the healpy PR may be blocked on the pkg-config bug that affected 4.6.0.

• Rebuild for cfitsio 4.4.1 ccfits-feedstock#16
• Rebuild for cfitsio 4.5.0 ccfits-feedstock#17
• Rebuild for cfitsio 4.6.0 ccfits-feedstock#18
• Rebuild for cfitsio 4.6.0 chealpix-feedstock#16
• Rebuild for cfitsio 4.5.0 disperse-feedstock#9
• Rebuild for cfitsio 4.6.0 disperse-feedstock#10
• Rebuild for cfitsio 4.6.0 fitsverify-feedstock#19
• Rebuild for cfitsio 4.6.0 healpix_cxx-feedstock#35
• Rebuild for cfitsio 4.6.0 healpy-feedstock#79
• Rebuild for cfitsio 4.4.1 hstcal-feedstock#26
• Rebuild for cfitsio 4.5.0 hstcal-feedstock#29
• Rebuild for cfitsio 4.6.0 hstcal-feedstock#31
• Rebuild for cfitsio 4.5.0 lalpulsar-feedstock#78
• Rebuild for cfitsio 4.4.1 lenstool-feedstock#24
• Rebuild for cfitsio 4.5.0 lenstool-feedstock#27
• Rebuild for cfitsio 4.6.0 lenstool-feedstock#28
• Rebuild for cfitsio 4.6.0 numcosmo-feedstock#82
• Rebuild for cfitsio 4.4.1 photospline-feedstock#44
• Rebuild for cfitsio 4.5.0 photospline-feedstock#45
• Rebuild for cfitsio 4.6.0 photospline-feedstock#46
• Rebuild for cfitsio 4.5.0 psrchive-feedstock#59
• Rebuild for cfitsio 4.6.0 psrchive-feedstock#61
• Rebuild for cfitsio 4.6.0 root-feedstock#287
• Rebuild for cfitsio 4.4.1 rubinenv-feedstock#284
• Rebuild for cfitsio 4.5.0 rubinenv-feedstock#294

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/cfitsio and so here I am doing that.

[h-vetinari]

The PRs for 4.6 are all roughly 2 weeks old, which isn't that long. But I won't stand in the way here, cleaning up these old migrators is definitely beneficial. Even more so if we keep more on top of them going forward. :)

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-webservice.

I was asked to ping @conda-forge/cfitsio and so here I am doing that.