bug: Missing cp314 wheel for Python 3.14

[bachya]

Summary

html-to-markdown v3.2.6 does not ship wheels built against the CPython 3.14 ABI (cp314), which makes it impossible to resolve as a dependency in Python 3.14 environments.

What we observed

When attempting to upgrade to v3.2.6 in a project that targets python_full_version == '3.14.4', uv fails to find a compatible wheel:

× No solution found when resolving dependencies for split (markers:
│ python_full_version == '3.14.4' and sys_platform == 'win32'):
╰─▶ Because html-to-markdown==3.2.6 has no wheels with a matching Python
    version tag (e.g., `cp314`) and etl depends on html-to-markdown==3.2.6,
    we can conclude that etl's requirements are unsatisfiable.

    hint: Wheels are available for `html-to-markdown` (v3.2.6) with the
    following Python ABI tags: `cp310`, `cp311`, `cp312`, `cp313`

The PyPI release for v3.2.6 confirms wheels are only available for cp310–cp313.

Expected behavior

A cp314 wheel is published for v3.2.6 (and ideally future releases) so that Python 3.14 users can install and resolve the package without issue.

Environment

• html-to-markdown version: 3.2.6
• Python version: 3.14.4
• Installer: uv

[Goldziher]

Already fixed on main (in flight prior to this report).

• Cargo.toml pins pyo3 = "0.28.3" with features = ["abi3-py310"] — wheels built with the abi3 stable ABI are forward-compatible with cp314.
• .github/workflows/ci.yaml test matrix already includes Python 3.14 (lines 467–481).
• packages/python/pyproject.toml declares the cp314 classifier and requires-python = ">=3.10".

The wheel published for v3.2.6 predates this work; the next release (currently rc.18 on main) will publish cp314 wheels — abi3 means the cp310 wheel itself loads on cp314, but a cp314-tagged wheel is also produced for clean resolver behavior under uv. Will close once the release ships.