chore(release): prepare v0.9.0 - #375
Merged
Merged
Conversation
Bump cross-module require versions to v0.9.0 via `make set-version` and assemble the five unreleased fragments into RELEASE-NOTES.md via `make release-notes VERSION=v0.9.0`. The root replace directives restored in #348 let `go mod tidy` resolve the not-yet-tagged sibling versions, so `make set-version` works as documented this time and no manual `go mod edit` was needed. Signed-off-by: Shimi Bandiel <shimib@google.com>
shimib
requested review from
RishabhSaini,
ahg-g,
evacchi and
jtechapps
as code owners
July 29, 2026 23:18
jtechapps
approved these changes
Jul 30, 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
2 participants
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.
Summary
Release prep for v0.9.0, following CONTRIBUTING.md → Preparing a release.
Two mechanical steps, both run from the documented targets — no hand edits:
1. Cross-module versions → v0.9.0
./go.modapi./go.modpipeline./go.modproducerpipeline/go.modapiproducer/go.modapiUnlike v0.8.0 (#348),
make set-versionworked as documented — the rootreplacedirectives restored in that same PR let
go mod tidyresolve the not-yet-taggedsibling versions, so no manual
go mod editwas needed.go.sumis unchanged.2. Release notes
The five unreleased fragments (#370, #371, #372, #373, #374) are assembled into a
RELEASE v0.9.0 2026-07-29section and deleted fromrelease-notes.d/unreleased/.#370 merged shortly before this branch was cut and is included.
Everything on
mainsince v0.8.0 is now recorded inRELEASE-NOTES.md.Verification
Run locally on this branch:
go build ./...at the root andGOWORK=off go build ./...inapi/,pipeline/,and
producer/— theGOWORK=offbuilds are the ones that regressed for v0.8.0,since they exercise resolution through the
replacedirectives rather thango.work.make ci— fmt, vet,golangci-lint(0 issues), release-notes lint, and the fullunit + integration test suite across all modules. All green.
After merge
Per CONTRIBUTING step 2, a maintainer tags the root module:
git tag v0.9.0 && git push origin v0.9.0CI - Tag Go Submodulesthen createsapi/v0.9.0,pipeline/v0.9.0, andproducer/v0.9.0.