Repository navigation
release: prepare the v0.3.0 source milestone - #165
Conversation
Cut the Unreleased changelog into 0.3.0 with a short summary of what landed since v0.2.0, and backfill the missing 0.2.0 entry. The status history moved from CLAUDE.md now sits unchanged at the end of the file. Point the README release coordinates at v0.3.0 and say plainly that `magpie --version` prints the crate version, 0.1.0. SECURITY.md no longer names each release, so it won't go stale at the next tag. Crate versions, the log format, and the standing policies are unchanged. The tag itself stays a separate owner action. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01EB1exYkc8Px1iG85NNWzxc
|
Warning Review limit reachedNext included review available in 13 minutes. View limit detailsLimit details: You’ve used the included review currently available. Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. Review configuration: ⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Free Run ID: 📒 Files selected for processing (3)
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing. Comment |
Prepares the tree for a
v0.3.0source release. Docs only.Changes
CHANGELOG.md: turns Unreleased into 0.3.0, with a short summary of what landed since v0.2.0: the CLI, portable verification in Rust, Python, and Go,LogWriteras the only write path, verified-replay projections, SQLite L0, checkpoint evaluation, and ADRs 0003–0010. Adds the missing 0.2.0 entry. The status history moved from CLAUDE.md sits unchanged at the end.README.md: the release coordinates point at v0.3.0 and say thatmagpie --versionprints the crate version, 0.1.0.SECURITY.md: no longer names each release, so it won't go stale at the next tag.Crate versions, the log format, and the standing policies are unchanged. Like v0.2.0, this is a source milestone. It is not the paused C3–C5 public pre-alpha.
After merge (owner): create the
v0.3.0release on the merge commit. The README's v0.3.0 link is a 404 until then.Validation:
git diff --check,python tools/check_release_metadata.py, andcargo package -p magpie-log --lockedpass. A script confirmed the moved changelog text is byte-for-byte identical.cargo testwasn't run: the change is docs only, and no test reads these files.🤖 Generated with Claude Code
https://claude.ai/code/session_01EB1exYkc8Px1iG85NNWzxc
Generated by Claude Code