chore: date changelog and cut v0.1.0 release (#102) - #103
Merged
Conversation
Move accumulated [Unreleased] entries into [0.1.0] - 2026-07-31, document the release workflow in CONTRIBUTING.md, and update SECURITY.md for the first tagged pre-release.
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
📝 WalkthroughWalkthroughThe documentation records the 0.1.0 release, defines release and support procedures, and adds release notes covering features, installation, prerequisites, and stability expectations. ChangesRelease documentation
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related issues
Suggested reviewers: 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CHANGELOG.md`:
- Around line 10-12: Complete the v0.1.0 release process for the version
declared in cli/pyproject.toml: create and push the v0.1.0 Git tag, publish the
corresponding GitHub Release, and update both changelog links to reference valid
release and comparison URLs.
In `@CONTRIBUTING.md`:
- Around line 106-114: Update the release checklist in CONTRIBUTING.md: after
moving entries into the versioned changelog heading, require the ## [Unreleased]
section to remain empty; require Step 3 to use release notes from the new
changelog section; and add a final step confirming the changelog compare links
resolve after the new tag is created.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 11c19bff-5b8e-4027-a5ae-71a02800fc3a
📒 Files selected for processing (3)
CHANGELOG.mdCONTRIBUTING.mdSECURITY.md
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@RELEASE_NOTES_v0.1.0.md`:
- Line 26: Update the v0.1.0 release flow and RELEASE_NOTES_v0.1.0.md so the
v0.1.0 tag is created and validated before publication, and ensure the tagged
CHANGELOG.md contains a finalized 0.1.0 section with a release date instead of
“TBD”. Keep the full changelog link pointed at the validated tag.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CONTRIBUTING.md`:
- Around line 110-116: Update the release workflow steps in CONTRIBUTING.md so
an existing vX.Y.Z tag is never reused for publishing. Require stopping to
verify the existing tag’s target against the merged release commit, and only
create and publish the GitHub Release after confirming the tag points to that
commit.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: ba589f53-38ad-4023-b44f-a554d8d2b838
📒 Files selected for processing (2)
CONTRIBUTING.mdRELEASE_NOTES_v0.1.0.md
🚧 Files skipped from review as they are similar to previous changes (1)
- RELEASE_NOTES_v0.1.0.md
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@CONTRIBUTING.md`:
- Around line 111-116: Update the release-tagging instructions around the
existing tag creation and validation steps to capture the peeled develop commit
with git rev-parse --verify 'develop^{commit}', create new tags explicitly on
that commit, and leave existing tags unchanged. Before pushing in either case,
compare git rev-parse --verify 'vX.Y.Z^{commit}' against the captured
release_commit rather than comparing annotated tag object IDs.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
wpak-ai
reviewed
Jul 31, 2026
wpak-ai
left a comment
wpak-ai
left a comment
Collaborator
There was a problem hiding this comment.
-
CONTRIBUTING.md:117,RELEASE_NOTES_v0.1.0.md:5- amend step 5 to nameRELEASE_NOTES_vX.Y.Z.mdas the--notes-fileartifact and add a checklist step that creates it -
CONTRIBUTING.md:96,CONTRIBUTING.md:104,SECURITY.md:9- delete the "ormainfor release fixes" clause so the whole doc set namesdevelopas the single branch that work, releases, and security fixes land on
3 tasks
bradjin8
changed the title
bradjin8
changed the title
Docs: plain-language release notes, active voice in SECURITY, colon instead of em dash in CONTRIBUTING. Code: walk up for image-registry.yml in run flow, share PLATFORM_CLI_MAP, remove unused helpers.
wpak-ai
approved these changes
Jul 31, 2026
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
2 participants
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
[Unreleased]entries into## [0.1.0] - 2026-07-31and reset[Unreleased]for post-release workSECURITY.mdsupported-versions table for the first tagged pre-releaseCONTRIBUTING.md(aligned with wg21-wiki-mcp conventions)Closes #102
Test plan
pre-commit run -apytest -m 'not integration'gh release create v0.1.0 --target develop --title v0.1.0 --notes-file RELEASE_NOTES_v0.1.0.md