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

I do have some suggestions for making it better though...

For recipe/meta.yaml:

• ℹ️ The recipe is not parsable by parser conda-souschef (grayskull). This parser is not currently used by conda-forge, but may be in the future. We are collecting information to see which recipes are compatible with grayskull.
• ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

_{This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/21754229653. Examine the logs at this URL for more detail.}

[cbourjau]

There are build failures on macOS x86 with Python 3.14. It is not clear to me what the issue may be. The tests seem to run fine. It is worth noting that there are official PyPI builds for macOS x86. However, there is currently no official upstream support for Python 3.14 on any platform. It wouldn't be the first time that we are ahead of upstream in terms of Python version support, though.

I wonder if it is worth debugging this or if we could simply drop macOS x86 from our huge build matrix at this point. What do you think @conda-forge/onnxruntime ?

[xhochy]

These failures could also be general OSX (including osx-arm64) failures. I wouldn't drop osx-64 because of that from the matrix. We aren't running tests for osx-arm64 in CI, thus we are not seeing them here.

Does Python 3.14 work on any other platform at all?

[cbourjau]

These failures could also be general OSX (including osx-arm64) failures. I wouldn't drop osx-64 because of that from the matrix. We aren't running tests for osx-arm64 in CI, thus we are not seeing them here.

Does Python 3.14 work on any other platform at all?

Thanks and good point! Let's revisit this after actually catching up with upstream, which sits at 1.23.2 (i.e. #164 )

[hmaarrfk]

sorry for taking the bots branch......

i asked the bot to regenerate it.

Unfortunately i've tried to debug the OSX stuf and couldn't figure out exactly which test fails....

i've asked the bot to regenerate.

I've also fallen into the trap of tryign to unvendor onnxruntime.... so now i'm about to give up...

[janjagusch]

@conda-forge-admin restart ci

[janjagusch]

@conda-forge-admin please rerender

[janjagusch]

Documenting the CI failure details here for future reference, as Azure Pipelines logs may no longer be accessible by the time someone looks at this.

This analysis was generated with Claude Opus 4.6.

CI Failure Analysis: SIGSEGV on osx-64 + Python 3.14

SIGSEGV on osx-64 + Python 3.14

Affected jobs:

• osx_64_python3.14.____cp314suffix (log)
• osx_64_python3.14.____cp314suffix-novec (log)

All Python tests pass successfully, but the test runner process crashes with SIGSEGV during teardown:

Ran 6 tests in 0.071s

OK
Traceback (most recent call last):
  File ".../tools/ci_build/build.py", line 2545, in <module>
    sys.exit(main())
  File ".../tools/ci_build/build.py", line 2454, in main
    run_onnxruntime_tests(args, source_dir, ctest_path, build_dir, configs)
  File ".../tools/ci_build/build.py", line 1682, in run_onnxruntime_tests
    run_subprocess([sys.executable, "onnxruntime_test_python_mlops.py"], cwd=cwd, dll_path=dll_path)
  ...
subprocess.CalledProcessError: Command '['.../bin/python', 'onnxruntime_test_python_mlops.py']' died with <Signals.SIGSEGV: 11>.

Hypothesis: This appears to be an upstream compatibility issue between onnxruntime v1.22.2's C++ extension module teardown and Python 3.14's changed module lifecycle on macOS x86_64. The actual tests all pass — the crash occurs during process exit/cleanup.

Also worth noting: onnxruntime v1.22.2 was never published to PyPI (releases go 1.22.0 → 1.23.0 → 1.24.1). This version only exists as a GitHub tag. Only the latest release (1.24.1) provides Python 3.14 wheels.

[cbourjau]

Upstream is currently broken on Python 3.14 (as of 1.24.2). Should be fixed on 1.24.3. See #169 for some more details.