Release setup: PyPI trusted publishers for the renamed coordinaxs-* distributions

[nstarman]

Follow-up to #548 (merged), which renamed the four sub-distributions to new PyPI project names. Because PyPI identity is per-project-name, trusted-publisher / OIDC config does not carry over — it must be created for each new name before the first release, or cd-publish.yml fails at the upload step (twine/OIDC does not catch this earlier; CI stays green and only the publish fails).

New project names (PyPI-normalized)

• coordinaxs-api
• coordinaxs-astro
• coordinaxs-hypothesis
• coordinaxs-interop-astropy

The main coordinax project name and the cd-publish.yml workflow identity are unchanged, so only these four need setup. coordinaxs.curveframes is intentionally unreleased (see RELEASING.md) and needs nothing here.

Checklist

• Create a pending/trusted publisher on PyPI for each of the four names, tied to cd-publish.yml and the pypi environment.
• Create a pending/trusted publisher on TestPyPI for each of the four names, tied to the testpypi environment.
• Verify a dry-run/TestPyPI publish succeeds end-to-end before cutting a real release tag.

Orphaned old projects (decision needed)

The pre-rename PyPI projects — coordinax-api, coordinax-astro, coordinax-hypothesis, coordinax-interop-astropy — are now orphaned. pip install coordinax-astro will keep serving the last old release indefinitely, shipping the old coordinax.astro module path (which no longer works against the renamed core).

• Decide: yank the old releases, and/or publish a final shim release under each old name with a deprecation notice pointing at the coordinaxs-* package.

References

• RELEASING.md — release process and the note on coordinaxs.curveframes
• scripts/validate_tag.py — PACKAGE_NAMES and the tag → package mapping
• .github/workflows/cd-publish.yml, .github/workflows/cd-coordinaxs-*.yml

🤖 Generated with Claude Code