chore(release): v1.0.10 - #20
Merged
Merged
Conversation
This was referenced Jul 27, 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
1 participant
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.
Version bump and changelog for v1.0.10. npm and the tag are already out; this lands the commit the tag points at.
The release workflow pushed this branch and then failed to open the PR: "GitHub Actions is not permitted to create or approve pull requests". That repo setting is off by default and is now on, so the next release opens its own PR. Opened by hand to unstrand master.
Merging as a merge commit. A squash would rewrite the commit and leave the tag outside master's history, which breaks the changelog range for the next release.