Prepare v3.6.0 release: notes + publishing doc#117
Merged
Conversation
Rename the Unreleased section to v3.6.0 with today's date and add the matching tag link reference. Rewrite the publishing how-to to use npm version (per the Release Process in the Version Control Standard) and add the GitHub Release step mandated by that standard.
This was referenced May 11, 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
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
## Unreleased→## [v3.6.0] — 2026-05-10inRELEASE_NOTES.mdand add the matching tag link reference.docs/dev/how-to/publishing.mdto align with the Version Control Standard's mandated release process:npm versionfor atomic bump+commit+tag, and an explicitgh release createstep so the GitHub Release accompanies every tag (per Mandate release notes and GitHub Release #112).Tracks #107 (acceptance criterion: "npm release published containing the merged updates").
Out of scope
scripts/release.shis now superseded bynpm version(per Use npm version for release workflow #100) and the publishing doc no longer references it. Cleanup of the script itself is deferred — file a follow-up if it isn't already covered by an existing automation issue.Test plan
npm run buildsucceeds on this branchnpm test— 105/105 pass on this branchnpm version minor→ push →npm publish→gh release create)