Repository navigation
Release v0.17.0 - #323
Merged
Merged
Release v0.17.0#323
Conversation
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.
Prepare v0.17.0 from the verified master checkpoint: bump package and lockfile root versions, move Unreleased changelog entries into the dated release section, and update documentation to describe the merged Context Engine foundation and release-candidate scope. Historical releases remain unchanged; v0.16.0 remains the latest published release until tagging/publication.
Homebrew remains explicitly unavailable and publishing stays disabled. The README mascot lockup, hosted reel, visual tour and installation guidance are preserved. Context Packs and broader capability scheduling remain upcoming. No runtime/test changes, tag, GitHub Release or tap publication are included.
Validation:
npm run verify:releasepassed (build, full canonical suite, diff checks, benchmark typecheck and timing smoke); docs asset tests passed; builtnode bin/nmsh --versionreports 0.17.0; package/lock changes verified as version-only. This metadata-only change does not add a physical terminal validation requirement.Merge through the protected PR path after required checks pass, then require successful CI on the resulting exact master commit before any tagging or publication.