Repository navigation
chore(release): v0.10.1 - #103
Merged
Merged
Conversation
Wasseing
approved these changes
Oct 5, 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
3 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.
Brings the v0.10.1 release commit (
80686f0) ontomain.On 2026-09-07 the release job created
80686f0and tagged it v0.10.1, but the push tomainwas rejected by the org ruleset "PCIDSS - Branch Protection" (GH013: Changes must be made through a pull request). The tag went through anyway, so 0.10.1 was published to npm from80686f0, whilepackage.jsononmainstayed at0.10.0.Since the release job computes the next version from
package.json, every merge since then tried to release 0.10.1 again and failed withfatal: tag 'v0.10.1' already exists.This cherry-picks
80686f0unchanged (package.json→ 0.10.1, CHANGELOG entry for #96), so the next release becomes 0.10.2.