ci: release workflow fixes (node + python)

[ArthurZucker]

Picks up the release-pipeline fixes that surfaced while tagging `v0.23.1rc0`. The version-bump commit on `v0.23-release` (PR #2032) is intentionally not included here — that one stays release-specific.

What's in here

• node-release.yml

  • `--zig` → `--cross-compile` (napi-rs/cli v3 renamed the flag).
  • Combine the universal macOS binary with `lipo` directly instead of `napi universal --dir …` (v3 dropped that syntax — `napi universalize` expects `napi artifacts` layout, `lipo` is the same thing the wrapper was running internally).
  • Add `napi create-npm-dirs` before `yarn artifacts` so target triples without a checked-in `npm//` template (e.g. `darwin-universal`) don't `ENOENT` at publish time.
  • Skip the `publish:` job on `rc*` tags (build + universal-macOS still run end-to-end), and bump its permission to `contents: write` so `napi prepublish` can create the GitHub Release on real releases.

• python-release.yml

  • Drop `3.14t` from the `windows-11-arm` matrix entry — `actions/python-versions` ships a broken `python-3.14.4-win32-arm64-freethreaded` package (0-byte `python.exe`).
  • Build proper non-abi3 wheels for 3.14t on the platforms that have a working free-threaded interpreter, via a `flavor: ft` discriminator. Each 3.14t row is a single YAML flow entry; the `--no-default-features --features pyo3/extension-module` and `--interpreter 3.14t` are derived from `flavor` in the maturin invocation.

• bindings/python/pyproject.toml

  • `requires-python` raised to `>=3.10` (matches the `abi3-py310` baseline; pip won't offer the wheel to 3.9 users).
  • Drop `Python :: 3.9` trove classifier, add `Python :: 3.14`.

Not in this PR

• The `update version and add locks` commits from `v0.23-release`. Those stay on the release branch.

[Copilot]

Pull request overview

Updates the Node and Python release GitHub Actions workflows to match upstream CLI/tooling changes and adjust release behavior, plus aligns Python packaging metadata with the project’s abi3 baseline.

Changes:

• Node release workflow: update napi-rs CLI flags, switch universal macOS build to direct lipo, add create-npm-dirs, and skip publishing on rc tags while allowing GitHub Release creation on stable tags.
• Python release workflow: restructure the build matrix to add free-threaded (3.14t) wheel variants via a flavor discriminator and drop the broken Windows ARM 3.14t entry.
• Python packaging metadata: raise requires-python to >=3.10 and update trove classifiers (drop 3.9, add 3.14).

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.

File	Description
bindings/python/pyproject.toml	Raises minimum supported Python version and updates trove classifiers.
.github/workflows/python-release.yml	Adds flavor-based matrix entries for 3.14t wheels and adjusts build args / artifact naming.
.github/workflows/node-release.yml	Updates cross-compilation flag usage, changes universal macOS combination strategy, and adjusts publish gating/permissions and packaging steps.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

actions/download-artifact without name will extract each artifact into its own subdirectory under ./bindings/node/artifacts. yarn artifacts / napi artifacts typically expects the .node files to be directly in the artifacts directory, so this layout can cause it to miss the binaries and fail at publish time. Consider setting merge-multiple: true (or downloading with an explicit pattern and merging) so the .node files land in a flat ./bindings/node/artifacts/ directory.

Suggested change

	path: ./bindings/node/artifacts
	path: ./bindings/node/artifacts
	merge-multiple: true

[Copilot]

For flavor: ft builds you set --interpreter to 3.14t, but actions/setup-python still installs the default 3.14 on macOS/Linux unless matrix.python-install is overridden. This will likely make maturin fail to find a 3.14t interpreter on at least the macOS flavor: ft matrix cells. Add python-install: "3.14t" (and any required python-architecture) to the flavor: ft include entries that run on host Python (macOS, and any non-container Linux builds).

[Copilot]

The free-threaded path disables default features but then enables --features pyo3/extension-module directly. Since this repo already defines a crate feature ext-module = ["pyo3/extension-module"] in bindings/python/Cargo.toml, using --features ext-module would be less coupled to the dependency name and easier to maintain if the feature wiring changes.

Suggested change

	${{ matrix.flavor == 'ft' && '--no-default-features --features pyo3/extension-module' || '' }}
	${{ matrix.flavor == 'ft' && '--no-default-features --features ext-module' || '' }}

[Copilot]

The job name reports matrix.interpreter || '3.14', but for the new flavor: ft matrix cells matrix.interpreter is unset, so these jobs will still display 3.14 even though the build is targeting 3.14t via the args expression. Consider deriving the displayed interpreter from matrix.flavor (or setting interpreter: "3.14t" on the flavor: ft include entries) to avoid confusion when debugging CI.

Suggested change

	name: build on ${{ matrix.platform || matrix.os }} (${{ matrix.target }} - ${{ matrix.manylinux || 'auto' }} - ${{ matrix.interpreter || '3.14' }})
	name: build on ${{ matrix.platform || matrix.os }} (${{ matrix.target }} - ${{ matrix.manylinux || 'auto' }} - ${{ matrix.flavor == 'ft' && '3.14t' || matrix.interpreter || '3.14' }})

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.