Repository navigation
chore(release): v0.3.0 distribution packaging (crates.io, binstall, brew, README, demo) - #212
Draft
hermanngeorge15 wants to merge 1 commit into
Draft
hermanngeorge15 wants to merge 1 commit into
hermanngeorge15 wants to merge 1 commit into
Conversation
…DME top, demo (#211) Packaging and docs only; no pattern or engine changes (freeze lifted for packaging, recorded in CLAUDE.md, .planning/STATE.md and .planning/ROADMAP.md). - Cargo.toml: readme, rust-version 1.88 (1.87 fails on a locked dependency), exclude list (crate drops from 448 to 190 files, 486 KiB compressed; the test corpus and the two docs the tests read stay in), binstall metadata resolving the existing raw release assets (#203) - release.yml: publish-crate job after the Release, crates.io trusted publishing via rust-lang/crates-io-auth-action, SHA-pinned (#204) - README: top 22 lines with badges, measured numbers, one-line installs and the demo; Installation section; pre-commit example pins v0.2.0 (#205) - docs/demo: VHS tape, 24.7 s GIF (913 KB), the skill file it scans; the code-scanning baseline accepts that file's planted PI001 line (#206) - docs/launch: Show HN and r/ClaudeAI drafts, directory lines, day-7 retro (#208, #209) - docs/reviews: the 2026-10-24 launch plan - CHANGELOG: Distribution section under Unreleased Verified locally: cargo publish --dry-run --locked, cargo binstall --dry-run resolves v0.2.0, actionlint, release_contract_test and catalogue_test pass, injection-scanner check README.md exits 0. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This was referenced Oct 25, 2026
Open
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.
Tracking: #211. Actions allowlist (org-level policy, owner only). CI on this branch is green (run 40183577009): the effective allowlist for this repo already holds
actions/checkout,dtolnay/rust-toolchain,actions/cache,taiki-e/install-actionandgithub/codeql-action/upload-sarif. The release workflow also needsactions/upload-artifact@*,actions/download-artifact@*,actions/attest-build-provenance@*,softprops/action-gh-release@*and, for the new job,rust-lang/crates-io-auth-action@*. The API refuses repo-level changes ("already set at the organization level"), so add those five in the org settings under Actions, Allowed actions, before tagging. SHA pinning stays required.2.
cargo publish --lockedat 0.2.0 from this branch, by hand, so the crate exists; then configure trusted publishing on crates.io forrelease.yml.3. Merge, bump to 0.3.0 with
Cargo.lock, promote[Unreleased]in the changelog, tagv0.3.0, followdocs/RELEASE-CHECKLIST.md. Then merge the tap branch after bumping the formula to 0.3.0.🤖 Generated with Claude Code