Skip to content

chore: Bump intra-repo deps to v0.11.0 and drop v0.9.0 retract#119

Merged
mojatter merged 2 commits into
mainfrom
chore/release-v0.11.0
May 9, 2026
Merged

chore: Bump intra-repo deps to v0.11.0 and drop v0.9.0 retract#119
mojatter merged 2 commits into
mainfrom
chore/release-v0.11.0

Conversation

@mojatter
Copy link
Copy Markdown
Owner

@mojatter mojatter commented May 9, 2026

Summary

cmd/s2-server is intentionally not bumped here. It needs to require github.com/mojatter/s2/server v0.11.0, but server is a new module without prior tags, and Go's workspace cannot resolve a not-yet-tagged require during local build (an MVS metadata fetch hits the proxy regardless of use directives). After this PR is merged and the v0.11.0 tags are pushed, a follow-up PR will bump cmd/s2-server/go.mod. Future releases (v0.12.0+) will not need this split since server will already be on the proxy.

Test plan

  • Tests workflow passes (root + s3 + gcs + azblob + s2env + server)
  • govulncheck workflow passes
  • e2e workflow passes

mojatter added 2 commits May 9, 2026 13:18
cmd/s2-server bump deferred to a follow-up PR: server is a new
module without prior tags, so workspace cannot resolve its require
before the tag is published.
v0.9.0 was 17 days ago and persisted across two minor cycles; any
remaining consumers have had ample warning. Closes #96.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove retract v0.9.0 from submodule go.mod files once aged out

1 participant