Bump version from 0.13.1 to 0.13.2 - #254
Merged
Merged
Conversation
Post-release dev-version bump. The release workflow's automated bump failed (its Contents-API commit was not GitHub-verified and the required-signatures ruleset rejected it); doing it manually as a verified commit while the workflow is fixed to use createCommitOnBranch.
Fab-Cat
approved these changes
Jul 12, 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.
Post-release dev-version bump to 0.13.2 (verified local commit). The Trigger Release run cut 0.13.1 fine (tag + release), but its automated bump 409'd on required-signatures: the Contents-API commit was not GitHub-verified. Recovering the bump here; the reusable workflow is being fixed to (a) use
createCommitOnBranch(always signed) and (b) treat the bump as best-effort (warn, don't fail the release).