chore(release): prepare v0.2.0 - #24
Merged
Merged
Conversation
- Cargo.toml/Cargo.lock version 0.1.0 -> 0.2.0 (pre-1.0 minor bump: this release carries two breaking changes - default port 3000 -> 8000 and MSRV 1.90 -> 1.93) - CHANGELOG: promote [Unreleased] to [0.2.0] - 2026-07-05 with fresh empty Unreleased section and updated compare links - README: health-response example version updated
- Cargo.toml: publish = false - cargo itself now refuses any publish, so the guarantee lives in the manifest, not just CI; documentation URL points at the GitHub Pages docs the release pipeline actually deploys instead of a docs.rs page that will never exist - release.yml: crates.io publish job removed - CLAUDE.md release section and CHANGELOG updated to record the policy
…gate Per review: the pipeline job stays as-is for future flexibility. The manifest-level publish = false remains the enforcement - cargo refuses to publish (verified via --dry-run), and the job's continue-on-error makes the step a harmless no-op on tagged releases.
Automated security review flagged the (pre-existing, repo-wide) mutable action tags when the publish job was restored. Recorded with a binding trigger rather than one-off pinning a single block: pinning is a repo-wide policy change belonging to a CI-focused pass. publish=false already neutralizes the CRATES_IO_TOKEN exposure path.
Self-updates from the latest semver tag, so the README never needs a manual version bump again; links to the releases page.
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
1 participant
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.
Version denotation for the security/SDK refresh that just merged (#23).
[Unreleased]promoted to[0.2.0] - 2026-07-05(the composite release notes), fresh empty Unreleased added, compare links updatedAfter merge, tagging
v0.2.0on the merge commit triggersrelease.yml(multi-platform builds, GitHub Release, docs deploy). The auto-generated release body will then be replaced with the curated CHANGELOG 0.2.0 section.