chore: release v1.6.0 - #246
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
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.
Pull Request
Description
Cuts
v1.6.0. Generated bychangie batch v1.6.0+changie merge— no hand edits.Version justification. Two independent signals agree on a minor bump:
Added(#243, #244), 1 ×Documentation(#245)git diff v1.5.2..main -- api/v1.txt→ +120, −0gorelease -base=v1.5.2Suggested version: v1.6.0, every entryaddedNo entry of the frozen
v1surface was removed or changed, so nothing here is a compatibility break.Type of Change
Release chore — none of the above. No source file changes; only
CHANGELOG.mdandchanges/.Checklist
make test) — no Go files changed; pre-commit skipped the Go hooks for that reasonmake vet— samemake lint) — samemake build) — samechangie new) — N/A, this PR consumes the fragmentsAdditional Notes
go.mod'sretract [v1.0.0, v1.4.0]block is untouched, so theVerify retraction blockCI step should pass and the retractions ship with this release.After merge, per RELEASE.md: sync
main, then tag the merge commit (not this branch) and pushv1.6.0to trigger the release build.By submitting this PR, I agree that my contributions will be licensed under the Apache License 2.0.