Rebuild for python 3.14

[regro-cf-autotick-bot]

This PR has been triggered in an effort to update python314.

Notes and instructions for merging this PR:

1. Please merge the PR only after the tests have passed.
2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.

---

If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

_{This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/17119519208 - please use this URL for debugging.}

[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/recipe.yaml) and found it was in an excellent condition.

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: failed

Thus the PR was not passing and not merged.

[synapticarbors]

@conda-forge-admin please rerender

[conda-forge-admin]

Hi! This is the friendly conda-forge automerge bot!

Commits were made to this PR after the automerge label was added. For security reasons, I have disabled automerge by removing the automerge label. Please add the automerge label again (or ask a maintainer to do so) if you'd like to enable automerge again!

[synapticarbors]

DO NOT MERGE - It appears as if the re-render dropped the 3.14 build. Need to investigate

[synapticarbors]

@conda-forge/core Why would re-rendering this feedstock remove all of the changes for the 3.14 migration? The migrations file is present.

[h-vetinari]

It's complicated... The migrator infrastructure is sensitive to the timestamps in the migrator files, which were reshuffled a few times because they also serve to order the sequence that migrations get applied. For more details: conda-forge/conda-smithy#2369

[h-vetinari]

@conda-forge-admin please rerender

[h-vetinari]

This still needs the fix from conda-forge/conda-smithy#2370 to be released (or rerender yourself with a dev version of smithy)