Repository navigation
docs: set the 1.0.0 release date in CHANGELOG.md - #5
Merged
Merged
Conversation
Samy-O7
approved these changes
Oct 22, 2026
Samy-O7
left a comment
Samy-O7
left a comment
There was a problem hiding this comment.
Approving. Checked:
- I ran the publish workflow's "Check tag, version and CHANGELOG.md" step against this branch: a
v1.0.0tag on main passes and writes 34 lines of release notes, while a wrong tag, a tag on an unmerged commit and the old(unreleased)heading all fail. package.jsonandsrc/version.tsare both 1.0.0.npm pack --dry-runlists 27 files (dist, README, LICENSE, NOTICE, CHANGELOG.md and package.json), with no tests, sources or source maps.npm audit --omit=devis clean, and the package has no runtime dependencies.
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.
Changes