chore(cmd/s2-server): Bump intra-repo deps to v0.11.1#131
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.
Step 3 (final) of the v0.11.1 release (see docs/releasing.md), following #130.
cmd/s2-serverhas noreplacedirectives, so itsGOWORK=offbuild (e2e image, GoReleaser) resolves intra-repo deps fromproxy.golang.org. It could only be pinned tov0.11.1once those tags were published (#130 + the pushed tags). This bumpss2,s3,gcs,azblob, andservertov0.11.1and refreshesgo.sum.Same sequence as v0.11.0 (#119 → #120).
Verification
Local, with the CI toolchain (
go1.25.10):GOWORK=off go build .passes (the e2e / GoReleaser build path).go test ./...passes (workspace mode).Next step
After merge, tag
cmd/s2-server/v0.11.1at the merge commit and push it, completing the v0.11.1 release.