docs: add v2.0.63 CHANGELOG entry and RELEASING.md#2502
Merged
Conversation
CHANGELOG.md gets a rollup entry covering v2.0.55..v2.0.63 in the project voice (bold lead-ins, [BREAKING] prefix with inline workaround, doc links to setup/lib/install-slug.sh, no PR numbers). RELEASING.md is new and documents the per-bump release policy starting with v2.0.63: tag every package.json bump, mirror the CHANGELOG entry into the GitHub Release body, append Contributors and (when relevant) New Contributors sections, and use rollup framing when multiple bumps collapsed into one release.
Two revisions in RELEASING.md based on review feedback:
1. Soften the "release per bump" claim. The policy is aspirational and
release publication is manual, so the opening now states the goal
("publish a GitHub Release for every package.json version bump that
lands on main") and acknowledges that there can be lag between a bump
merging and the release being cut. Intent: timeliness, not strict 1:1.
2. Add a "Channels and stability" section that explicitly states NanoClaw
ships a single channel today, distinguishes latest/stable/pinned for
consumers, and reserves space for a future pre-release channel without
inventing structure that does not yet exist. Folds the previous Pinning
section into the new structure as the Pinned bullet.
The "For detailed release notes, see the full changelog on the documentation site" line pointed at a docs portal that does not exist. CHANGELOG.md is the canonical record, so the header now says only what is true: all notable changes are documented in this file.
This was referenced May 16, 2026
8 tasks
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.
Summary
CHANGELOG voice match
The new entry follows the existing CHANGELOG conventions:
[BREAKING]prefix on the service-name change, with the workaround inline (no link-out for the fix).[setup/lib/install-slug.sh](setup/lib/install-slug.sh).on_wakegraceful startup).RELEASING.md contents
Covers:
package.jsonbump that lands onmain, with releases cut manually by a maintainer. Acknowledges lag between bump and release; intent is timeliness, not strict 1:1.[BREAKING]prefix conventions, doc-link style, no PR numbers in prose.Commits
Follow-up
Once this lands on
main, the v2.0.63 draft GitHub Release body should be updated to mirror the CHANGELOG entry verbatim and link to RELEASING.md at the new relative path. The release body draft is staged atrelease-v2.0.63/release-body.mdin the maintainer's workspace.If/when #2403 (Release workflow) lands, RELEASING.md should be updated in that PR to reference the workflow and its gates.
Test plan
[setup/lib/install-slug.sh](setup/lib/install-slug.sh)resolves.