Repository navigation
docs(release): notes for v0.1.10 - #43
Merged
Merged
Conversation
Signed-off-by: Adao Oliveira Jr <junior@users.noreply.github.com>
Signed-off-by: Adao Oliveira Jr <junior@users.noreply.github.com>
pierreneter
approved these changes
Nov 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
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.
Release notes for v0.1.10, as
docs/releases/v0.1.10.md.release.ymlreads that file from the tagged commit, so this merges last, right before the tag.They are written for a release of #40 and #41 (merged), #39 and #44. If #39 or #44 does not make it, its part comes out before this merges, and anything else that merges first gets its section here.
govulncheck is clean on main today (ed98435, Go 1.27.4); I will run it again on the commit that gets tagged.