chore: prepare v1.4.0 release notes - #37
Merged
Merged
Conversation
coderwhy
marked this pull request as ready for review
August 17, 2026 09:49
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.
Summary
Prepare the repository for a future
v1.4.0release.1.4.0mainCHANGELOG.mdin the published npm packageWhy
The current npm release is
1.3.1(published in 2023), while the completed maintenance work is ready to be documented for the next release. This PR creates a reviewable release-preparation step without publishing anything.User impact
Consumers can review the upcoming behavior changes and compatibility notes before publication. The package adds no runtime dependencies and keeps its CommonJS entry point unchanged.
Validation
npm test: 14/14 passingnpm audit --audit-level=low: 0 vulnerabilitiesnpm pack --dry-run: passing; package contents verifiedgit diff --check: passingRelease boundary
Merging this PR does not create a GitHub Release or publish to npm. Those remain separate, explicitly confirmed actions.