rdocx: Command for Claude Code

/release {vX.Y.Z | rpptx-vX.Y.Z}

Release one complete Rust, CLI and Python family from the exact main merge commit produced by /close-sprint. This command alone may create or push a release tag or start crates.io and PyPI publication. It never edits versions, merges branches, or creates a sprint tag. Historical py-* tags remain immutable and readable, but cannot start a new publication.

Family contract

For vX.Y.Z, the selected crates.io set is exactly rdocx-opc, rdocx-oxml, rdocx-layout, rdocx-html, rdocx-pdf, rdocx, and rdocx-cli. The selected Python project is rdocx from rdocx-py. For rpptx-vX.Y.Z, the selected crates.io set is exactly oxml-core, oxml-opc, oxml-media, oxml-layout, oxml-drawing, oxml-pdf, oxml-sml, oxml-cli-support, oxml-chart, rpptx-oxml, rpptx-chart, rpptx-layout, rpptx-render, rpptx, and rpptx-cli. The selected Python project is rpptx from rpptx-py. The exact selected Rust manifests, workspace dependency pins when present, binding crate and pyproject.toml version must match X.Y.Z. Binding and WASM crates are not published to crates.io. Each release contains six selected CLI archives, six cp39-abi3 wheels, one source distribution and one SHA256SUMS covering all thirteen payloads.

Preconditions

Refuse before any tag or push if one check fails:

1. The argument is exactly vX.Y.Z or rpptx-vX.Y.Z, with no suffix or extra prefix. Run python3 scripts/sprint_workflow.py unified-release-family <requested-tag> and inspect all selected version carriers and exact package allowlists.
2. The current branch is clean main, at the same SHA as origin/main. The sprint that prepared this release has already closed through /close-sprint, and its sNN tag points to this exact merge commit. The selected release preparation F-ID is done in the sprint delivery records and its plan is completed. All its dependencies are done.
3. The committed sprint review is clean at the reviewed sprint SHA and the /close-sprint report records the merge. Compare the merge commit tree with that reviewed sprint tree. Only the reviewed close-sprint tracker summary may differ. Refuse a material source, release-workflow, command, changelog, manifest, lockfile, or HLD difference. Do not run /sprint-review on main, because that command writes tracked review files.
4. Consume the closed sprint's authenticated full verification at producer H and its validated completion/review metadata at R when this clean main merge M has exactly R's Git tree and all relevant tools, oracle inputs, configuration and retained artifacts remain unchanged. Use the existing closure_evidence_problems(load(sprint), reviewed_R) check and step3's actual main/review tree comparison. Current clean main, origin/main and sprint tag identities remain required. Record H, R and M truthfully. Do not claim the commands ran at M or repeat them merely because merging changed the commit SHA. No new cache service or command bridge is needed. A latest failed full attempt blocks reuse of an older green one. Missing evidence, a material tree delta or changed inputs requires the missing or invalidated gates. Both requested families reuse this common applicable full evidence. Fresh registry, publisher and approval checks remain due.
5. Run python3 scripts/sprint_workflow.py release-notes <requested-tag> --check, render the exact CHANGELOG.md body, and inspect the family-only claims, compatibility guidance, included issue and pull-request links, and authenticated contributor credit. Rebuild the selected contribution inventory from reviewed evidence.
6. Consume the actual locally patched publication dry run included in step4's applicable full evidence, with its retained verified archives and exact 22-package union below10MiB. Do not execute it a second time. Confirm the selected family's crates.io versions and PyPI version are freshly absent. A duplicate or partial prior publication is a failed release.
7. Inspect .github/workflows/wheels.yml. Its tag path must select exactly one Rust allowlist, one CLI binary, and one Python distribution, validate six CLI archives and seven Python artifacts, verify their provenance, publish through the pypi environment and create one GitHub release only after both registries succeed. The PyPI trusted publisher for the selected project must identify this repository, wheels.yml, and environment pypi, with no long-lived token.
8. Fetch the remote tag namespaces. The requested tag must be absent locally and on origin. Confirm the selected crates.io and PyPI owner or maintainer roles that will be checked after publication.