chore(release): prepare v0.2.0#655
Merged
Merged
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
🚧 Files skipped from review as they are similar to previous changes (1)
📝 WalkthroughWalkthroughThe PR bumps workspace and package versions to 0.2.0, updates release and install documentation, adds v0.2.0 release and verification packets, and expands CLI-doc validation to accept command-family prefixes and run script tests in preflight. ChangesRelease metadata and documentation
Estimated code review effort🎯 2 (Simple) | ⏱️ ~15 minutes Possibly related PRs
Suggested labels
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
🔍 The Case of Pull Request #655Schema Sets
Schema Set
|
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 054a5e6a74
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
Owner
Author
Code Lawyer Activity Summary
Verification
Resolved review thread: |
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.
Linked Issue
Tracks #625. Do not auto-close on merge; close #625 only after the signed
v0.2.0tag is cut from syncedmainand the release publication checks pass.Branch / Issue-Title Check
release/v0.2.0is a release-prep branch, not an issue-title slug.Summary
v0.2.0release truth before tagging frommain.0.2.0.v0.2.0release packet, verification packet, and user-facing release notes.v0.2.0release boundary.wesley configare valid when concrete subcommands exist.Why
Wesley releases must come from tagged
main, with README, changelog, release notes, runbooks, version metadata, and release evidence already merged before the tag is cut. This PR makesmaintruthful forv0.2.0without adding domain semantics to Wesley core.Changes
wesley-holmes, root private package metadata, andCargo.lockare aligned to0.2.0.docs/method/releases/v0.2.0/release.md,docs/method/releases/v0.2.0/verification.md, anddocs/releases/v0.2.0.md.README.md,docs/GUIDE.md,docs/ENTRYPOINTS.md,docs/TECHNICAL_TEARDOWN.md, docs site pages, and release indexes.v0.2.0examples withvX.Y.Zplaceholders where the docs describe generic future release mechanics.Method Evidence
Tracker Hygiene
v*scheduling labels or exact-version title/body text that self-blocksrelease-prep-guard.triage:cool-ideas; it is already scheduled forv0.3.0.Docs Topics Audit
docs/topics/for release-relevant accuracy and coverage.docs/topics/page required content correction after audit; related stale signposts and command-checker behavior were corrected outsidedocs/topics/.Risk
release-prep-guard, package crate dry-run, lockfile checks, version smoke, and release verification docs.Backout
Use a merge revert of this PR before tagging. Do not tag
v0.2.0until the revert lands andmainis synced. If the tag has already been pushed, treat that as a release incident: stop publication if possible, document the exact state, and cut a corrective follow-up release rather than rewriting public history.Testing
cargo xtask release-prep-guard --version 0.2.0cargo xtask preflightcargo xtask release-checkcargo xtask package-crates --version 0.2.0RUSTDOCFLAGS='-D warnings' cargo doc --workspace --no-depsBATS_LIB_PATH=test/vendor bats -t test/release-governance.bats test/docs-planning-boundary.batsnode scripts/check-doc-cli-commands.mjscargo xtask docs-checkpnpm exec prettier --check ...on changed docs/scripts/metadatacargo run --bin wesley -- --versionprints0.2.0cargo test --workspace -- --listlists 323 Rust testsEvidenceMap / SourceMap (if applicable)
Not applicable. This PR does not change SQL-to-SDL mapping, EvidenceMap, or SourceMap behavior.
Screenshots / Logs (optional)
Not applicable.
Merge Strategy
main, create a signedv0.2.0tag frommain, runcargo xtask release-guard --tag v0.2.0, push the exact tag, and monitor release publication.Checklist
cargo xtask preflight)cargo xtask release-checkandcargo xtask release-prep-guard --version 0.2.0)Pre-Tag Sign-Off for
v0.2.0Reviewer: @
Date: 2026-06-26
Human-Review Items
CHANGELOG reflects actual diff
I ran
git log v0.1.1..HEAD --onelineand confirmed that theCHANGELOG.mdentry for this release accounts for all user-visible changes. No significant change is silently absent from the entry.docs/ARCHITECTURE.mdis currentI read
docs/ARCHITECTURE.mdand confirmed it accurately describes the current repository structure, crate relationships, and ownership boundaries. No crate, package, or boundary described has been removed, renamed, or fundamentally changed without the doc being updated.Guide claims are accurate
I spot-checked the guides in
docs/guides/that are relevant to changes in this release. Commands, flags, file paths, and behavioral claims match the current codebase. I did not rely solely on the automated path/SHA checks.docs/topics/accuracy and coverage gate is metI audited every tracked file under
docs/topics/for release-relevant accuracy and coverage. At least 90% accuracy of audited topic claims and at least 90% coverage of release-relevant contributor/operator topic workflows are met. Any stale topic claim, obsolete instruction, missing topic, or missing authoritative link was corrected before tagging.No known issues being silently shipped
I reviewed the open GitHub Issues for known defects or outstanding decisions that affect this release's correctness or safety, whether or not they are already marked as release issues. Anything knowingly deferred is acknowledged in the CHANGELOG or a documented follow-on issue.
Tagged
mainis the release boundaryI confirmed every repo-resident release fact that must ship with this version is already on synced
mainbefore tagging. The release does not depend on a manual post-publish merge to make README, changelog, release notes, runbooks, or verification docs accurate.Summary by CodeRabbit
New Features
Bug Fixes
Documentation