Skip to content

chore(release): remove the manual crate publication path - #65

Merged
zoeyrose merged 1 commit into
mainfrom
chore/remove-manual-crate-publication
Nov 14, 2026
Merged

zoeyrose merged 1 commit into
mainfrom
chore/remove-manual-crate-publication

Conversation

@zoeyrose

Copy link
Copy Markdown
Member

Summary

Removes the manual 0.2.0 crate publication path so the automatic release contract is the only way a crate version is published.

  • publish-crate.yml: drops the prepare, verify and publish jobs and the source_tag input; operation now only accepts automatic. The automatic-verify and automatic-publish jobs are byte-for-byte unchanged, and the inputs that crate_release.py dispatch sends (operation, source_release_id, source_revision, manifest_sha256) are all still declared.
  • Deletes tools/crate_publication.py, tools/crate_upload.py, their tests and policy/rust-crate-next.json.
  • Moves the packaged-crate archive check that tools/validate.sh uses into tools/crate_archive.py (version is now a required argument) with its own test.
  • check-crate-release-policy.py: new SHA-256 anchor for the reduced workflow, no next-artifact pin check, candidate publication is always reviewed-automatic-publication.
  • README and AGENTS.md: 0.2.0 is described as historical lineage, pinned in policy/crate-release.json.

Review notes

  • The workflow anchor change is deliberate and needs the independent review the checker comment asks for.
  • AGENTS.md previously said to preserve the manual path as historical evidence; this PR changes that sentence on the maintainer's instruction.
  • The automatic dispatch path is only exercised by the next crate release, so CI on this PR does not prove it end to end.

Validation

python3 tools/check-crate-release-policy.py and the Python suites listed in tools/validate.sh pass locally. The cargo, Go and packaging parts of tools/validate.sh were not run locally (no toolchains in the authoring environment) and rely on Protocol validation in CI.


Generated by Claude Code

Crate versions after 0.2.0 publish only through the automatic release
contract, so the manual prepare/publish workflow operations, their tooling
(crate_publication.py, crate_upload.py), the 0.2.0 next-artifact policy
and their tests are removed. The packaged-crate archive check that
validate.sh still needs moves to tools/crate_archive.py. The publication
workflow anchor in check-crate-release-policy.py is updated for the
reduced workflow, and the README and AGENTS.md describe 0.2.0 as
historical lineage only.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BPTYAokoQXfhC9D2iVv8B6
@github-actions

Copy link
Copy Markdown

Dependency Review

✅ No vulnerabilities or license issues found.

Scanned Files

  • .github/workflows/publish-crate.yml

@zoeyrose
zoeyrose merged commit eea6fc7 into main Nov 14, 2026
9 checks passed
@zoeyrose
zoeyrose deleted the chore/remove-manual-crate-publication branch November 14, 2026 21:34
@github-actions

Copy link
Copy Markdown

🎉 This PR is included in version 2.26.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants