chore(release): prepare v0.8.0#348
Open
shimib wants to merge 3 commits into
Open
Conversation
Bump cross-module require versions to v0.8.0 and assemble the six unreleased release-note fragments into RELEASE-NOTES.md. Versions were edited manually (go mod edit) rather than via `make set-version`, because llm-d#328 removed the root replace directives in favor of go.work: `go mod tidy` ignores go.work, so it cannot resolve the not-yet-tagged sibling versions. See llm-d#328 for the follow-up. Signed-off-by: Shimi Bandiel <shimib@google.com>
shimib
requested review from
RishabhSaini,
ahg-g,
evacchi and
jtechapps
as code owners
July 24, 2026 16:38
llm-d#328 replaced the root replace directives with go.work and made the Dockerfile drop ./producer. But go.work overrides module *source*, not the module-graph version requirement, and `go mod tidy`/`docker build` ignore it — so any bump to a not-yet-tagged version (e.g. v0.8.0) fails to build (PR container-build, release image build, and `make set-version`). Restore the three root replace directives and revert the Dockerfile to COPY producer/ so all siblings resolve locally without needing tags. go.work is kept for IDE/dev; llm-d#328's lint fix and Makefile tweaks are retained. See llm-d#328 for the broader discussion. Signed-off-by: Shimi Bandiel <shimib@google.com>
The assemble-release-notes script left a trailing blank line that the end-of-file-fixer pre-commit hook rejects. Signed-off-by: Shimi Bandiel <shimib@google.com>
This was referenced Jul 24, 2026
jtechapps
approved these changes
Jul 24, 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
3 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.
What does this PR do?
Prepares the v0.8.0 release and restores the release build flow that #328 broke.
Release prep
requireversions tov0.8.0(root +pipeline+producer).RELEASE-NOTES.mdunderRELEASE v0.8.0.Release-build fix (targeted partial revert of #328)
replacedirectives.COPY producer/(drops thego work edit -dropuse ./producerstep).#328 swapped the root replaces for
go.work, butgo.workoverrides module source, not the module-graph version requirement — andgo mod tidy/docker buildignore it. So bumping to a not-yet-tagged version failed everywhere: PRcontainer-build, the tag-time release image build, andmake set-version. Restoring the replaces makes all siblings resolve locally without needing the tags.go.workis kept for dev; #328's lint fix and Makefile tweaks are retained. A fullgit revertof #328 was avoided because it would reintroduce thegochecknoglobalslint failure #328 fixed. See #328 for discussion.Validated locally: workspace
go build/go vet,GOWORK=off go build,go mod tidy(no-op), and a fulldocker buildall pass.Release steps after merge
Release note