Repository navigation
ver: bump to v0.9.69 - #241
Merged
Merged
Conversation
The release workflow cuts a release only when a version bump is the commit merged last, and the merge that bumped to v0.9.69 ended on a changelog commit, so v0.9.69 was never released. This empty bump is the commit it releases from; the version is already 0.9.69. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Simon A. F. Lund <os@safl.dk>
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.
Releases cijoe v0.9.69. #240 bumped the version but merged with a changelog commit last, and the release workflow only releases when the last commit is the
ver: bump, so v0.9.69 was skipped. This is an emptyver: bump to v0.9.69on top of main.Not tested: nothing to test; the tree is unchanged.
Assisted-by: Claude Code:claude-opus-5-5