Repository navigation
chore!: prepare 2.0.0-rc.1 and validated tag-based releases - #13
Merged
Merged
Conversation
BREAKING CHANGE: Node.js 22 or newer is now required.
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
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.
Require Node.js 22+ and prepare
2.0.0-rc.1with consistent lint/format checks and at least 98% global coverage. Fix evaluation timeout leaks so the test runner exits normally.Release candidates publish to
nextwhilelateststays at1.0.7. The release workflow validates the tag against the package version and changelog, tests Node.js 22/24, and publishes the exact archived package that passed validation. GitHub releases use the validated commit and mark RCs as prereleases. Remove the broken duplicate manual release workflow and local publish steps.CI follow-up: remove the optional bundle-size PR comment that failed with HTTP 403, while retaining bundle size enforcement and console reports. Keep the two Claude workflows byte-identical to production because the app rejects PR authentication when those workflow files differ; document their narrow Prettier exception.
Validation:
npm run quality:check: lint, formatting, build, bundle limits, and 1,128 passing tests (one pre-existing skip).Rollout: merge this PR after the required review, then tag the merged commit
v2.0.0-rc.1to publish tonext. Verify the registry-installed RC in the sample apps before preparing and tagging stable2.0.0. The Node.js minimum is a breaking compatibility change; older runtimes should remain on 1.x.