Repository navigation
chore(release): remove the manual crate publication path - #65
Merged
Merged
Conversation
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
Dependency Review✅ No vulnerabilities or license issues found.Scanned Files
|
|
🎉 This PR is included in version 2.26.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 theprepare,verifyandpublishjobs and thesource_taginput;operationnow only acceptsautomatic. Theautomatic-verifyandautomatic-publishjobs are byte-for-byte unchanged, and the inputs thatcrate_release.py dispatchsends (operation,source_release_id,source_revision,manifest_sha256) are all still declared.tools/crate_publication.py,tools/crate_upload.py, their tests andpolicy/rust-crate-next.json.tools/validate.shuses intotools/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 alwaysreviewed-automatic-publication.policy/crate-release.json.Review notes
Validation
python3 tools/check-crate-release-policy.pyand the Python suites listed intools/validate.shpass locally. The cargo, Go and packaging parts oftools/validate.shwere not run locally (no toolchains in the authoring environment) and rely onProtocol validationin CI.Generated by Claude Code