Bump onnxruntime to 1.24.4 and add Python 3.14

[jviehhauser]

Summary

• Bumps onnxruntime from 1.24.2 to 1.24.4
• Adds Python 3.14 support (drops Python 3.10 — upstream now requires >= 3.11)
• Switches Linux runners from decommissioned cirun-openstack-cpu-4xlarge to Cirrus runners (ghcr.io/cirruslabs/ubuntu-runner-amd64:24.04-lg)
• Removes deprecated self_hosted from conda-forge.yml (fixes linter warning)
• Re-rendered with conda-smithy 3.59.0

Motivation

The Python 3.14 migration PR (#163) was blocked by a segfault in onnxruntime on Python 3.14 (upstream issue microsoft/onnxruntime#27392). This was fixed upstream in v1.24.3 via microsoft/onnxruntime#27413 (refcount bug in map input conversion). The reporter confirmed the fix on win-64, linux-64, and osx-arm64.

v1.24.4 is a patch release containing additional bug fixes. It also bumps python_requires to >= 3.11, so Python 3.10 is dropped from the build matrix.

All 4 existing patches were verified to still apply cleanly to v1.24.4.

CI runner changes

The Quansight Open GPU Server (OpenStack) was decommissioned on 2026-03-13 (conda-forge/.cirun#174), causing all Linux GHA jobs to time out after 24h waiting for runners that no longer exist. This PR switches Linux builds to Cirrus runners (access granted via conda-forge/admin-requests#1982). Windows builds remain on cirun-azure-windows-4xlarge.

Supersedes #163 and #176.

Test plan

• osx-arm64 builds pass (all Python versions including 3.14)
• Linux builds pass on Cirrus runners
• Windows builds pass on cirun-azure
• Python 3.10 builds are correctly skipped

[conda-forge-admin]

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

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

• ❌ In conda-forge.yml: $.github_actions = {'self_hosted': True, 'timeout_minutes': 720, 'triggers': ['push', 'pull_request']}.

  {'self_hosted': True, 'timeout_minutes': 720, 'triggers': ['push', 'pull_request']} is not valid under any of the given schemas

  Schema

  {
    "anyOf": [
      {
        "$ref": "#/$defs/GithubActionsConfig"
      },
      {
        "type": "null"
      }
    ]
  }

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/23869425105. Examine the logs at this URL for more detail.}

[jviehhauser]

@conda-forge-admin, please rerender

[conda-forge-admin]

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

I tried to rerender for you, but it looks like there was nothing to do.

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

[conda-forge-admin]

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

I tried to rerender for you, but it looks like there was nothing to do.

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

[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/24079976141. Examine the logs at this URL for more detail.}

[cbourjau]

Do we expect the GitHub-hosted runners to be beefy enough to build the CUDA builds? Either way, the cirun ones are still referenced here. I don't think that this is ready, is it?

[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: passed
• github-actions: failed

Thus the PR was not passing and not merged.

[cbourjau]

conda-forge/admin-requests#1982 provides an alternative for the Linux runners, but I'm not sure what the solution for Windows is, yet. Either way, this PR is not ready to be merged.

[jviehhauser]

Updated to switch Linux builds to Cirrus runners (see also conda-forge/.cirun#174). Windows builds remain on cirun-azure-windows-4xlarge for now.