[rwgk]

Summary

Release one bindings line and its matching metapackage from the package configuration recorded in the release tag.

• Separate workflow-control tools from tagged source, and qualify release checkouts as tag refs.
• Require successful exact-tag/exact-SHA CI and validate artifact identity, versions, and the complete tagged Python/platform wheel matrix.
• Require exact-version notes in the tagged component source, preserving each component's empty-note and post-release policy.
• Preserve Pathfinder's draft preparation, documentation, both-index verification, final publication, and noncanceling release locks.
• Keep bindings releases independent of builds/releases of the other bindings major, Core, and Pathfinder; use published dependencies where appropriate.

The new tooling supports tagged sources containing the new configuration. Older immutable releases remain unchanged and require their compatible historical tooling for reruns.

Stack / Review Boundary

Layer 6 of 8. Previous: #3176. Next: #3178. All layers and integrated validation.

After #3173, #3174 through #3176 form one merge group, reviewed separately and validated at #3176. This release-routing layer follows that group; #3178 adds maintenance policy, and #3182 isolates the optional runtime fixes and contains the final integrated source state. The stack retains main baseline dfad7e3658a9. Current cumulative validation is recorded below and in #3178.

Suggested Review Order

1. .github/workflows/release.yml
2. ci/tools/lookup-run-id
3. ci/tools/validate_release_wheels.py
4. ci/tools/check_release_notes.py
5. .github/RELEASE-core.md

Validation

Full hosted CI passes at #3176, and Full hosted CI passes at #3182, including this layer's release-routing changes. Release publication itself was not exercised by these PR runs.

The current #3182 head passes 436 CI-tool tests and 55 subtests, including 61 release-note cases. Six local CLI integration checks exercise the resolver-to-release-notes sequence for both bindings majors, both matching metapackages, Core, and Pathfinder. Full local pre-commit passes at the final #3182 head, including actionlint and Lychee.

The merge preserves Pathfinder's requirement for a notes file even for post releases, its allowance for empty notes, and successful version output. Explicit publication gates preserve resolver and documentation failures as blockers while allowing other components to skip Pathfinder-only jobs. An independent review found no merge regressions.

Tagged-source routing, artifact identity, complete wheel matrices, SCM progression, and standalone packaging remain covered by the existing tests and earlier isolated rehearsals. No hosted release dry-run, remote tag creation, release upload, or package publication was performed for this rebase.

Checklist

• Relevant existing and focused regression tests cover the integration behavior.
• This description identifies the layer's scope and validation boundary.

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.