chore: release v0.5.19#68
Merged
Merged
Conversation
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.
Patch release bumping
0.5.18→0.5.19.Includes the merged bugfix:
Bumps
.versioninbuild.zig.zonandpub const versioninsrc/main.zigso they match thev0.5.19tag (required by therelease.ymlversion guard). Publishing happens when thev0.5.19tag is pushed onto the merge commit, which triggers the release workflow to build the target binaries and publish the GitHub release.Release details
main@9decda8(1 commit ahead ofv0.5.18, the fix: stop libghostty stream logs from corrupting the boo ui viewport #65 fix).v0.5.19and push it to triggerrelease.yml.gh release create --generate-notes.