Repository navigation
chore: release 0.2.0 as first stable version - #16
Merged
Merged
Conversation
commit: |
gioboa
approved these changes
Oct 8, 2026
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
2 participants
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.
Adds a minor changeset so the next release is
0.2.0.0.1.0was published to npm on 2026-07-30 and later unpublished. npm never lets an unpublished version number be reused, so publishing0.1.0fails withCannot publish over previously published version "0.1.0"(run).0.2.0ships the same changes as the first stable release onlatest.After merging:
latestand merge the generatedRelease v0.2.0PR.0.2.0.