Repository navigation
chore: prepare stable Node 22 release 2.0.0 - #14
Merged
Merged
Conversation
|
Claude encountered an error —— View job I'll analyze this and get back to you. |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
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.
Promote the validated
2.0.0-rc.1implementation to2.0.0. Update package metadata and migration/release documentation for the Node.js 22 minimum; the public API and runtime source are unchanged from the RC.Validation:
next;latestremains1.0.7. Registry checksum matches the artifact validated by Release CI on Node.js 22 and 24.Rollout after review and merge:
NPM_TOKENhas publish access to this package before tagging; RC CI publishing failed with E404. The exact CI artifact was instead published using the owner's authenticated npm session.v2.0.0. Release CI validates Node.js 22/24 and publishes the tested artifact tolatest.npm dist-tag add rule-engine-js@1.0.7 latest.No stable tag or npm publication has been created yet. Production requires one approving review. The existing Claude bot OAuth credential also needs renewal; it is separate from the quality gates.
RC release: https://github.com/crafts69guy/rule-engine-js/releases/tag/v2.0.0-rc.1