Repository navigation
Prepare v0.7.0 release - #74
Merged
Merged
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
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.7.0 with the baseline lifecycle feature and deterministic baseline ordering. The changelog identifies the Node.js 22 CLI floor as a breaking change, and package, lockfile and generated version metadata agree.
Local Node.js 22.23.3 and 24.22.0 runs passed with 119/119 tests each, 92.89% statement/line coverage, 83.24% branch coverage and 98.48% function coverage. Lint, full audit, package smoke, standalone Action and workflow lint passed. Hosted Node.js 20/22/24 tests, macOS/Windows checks, CodeQL, Dependency Review and Snyk passed. Tag v0.7.0 and npm package 0.7.0 with provenance are published, and the GitHub Release is live.