chore(release): prepare 0.6.1 - #86
Merged
Merged
Conversation
Align the npm package, lockfile, and all public host manifests on version 0.6.1, and document the Inspector Replay, trace, navigation, matching, and public-demo changes since 0.6.0. Validated with npm ci, two complete 1,309-test runs, package verification for 511 npm and 533 runtime entries, and a successful npm publish dry-run for the 0.6.1 tarball. Co-authored-by: Codex (GPT 5.6 Sol) <codex@openai.com>
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
Validation
npm cinpm test— 92 files, 1,309 testsnpm run pack:verify— 511 npm entries, 533 runtime zip entriesnpm run publish:dry-run— 511-file 0.6.1 tarball, 2.5 MB packed / 6.4 MB unpacked, npmjs latest targetgit diff --checkRelease gate
Do not merge until the exact PR head passes Linux Node 22.20.0, macOS Node 22.20.0, Windows Node 22.20.0, and Linux Node 24.x. After merge, tag that exact main commit as
v0.6.1, publish from the tag/main commit through the trusted release workflow, and verify registry metadata plus a cold CLI invocation.