-
Notifications
You must be signed in to change notification settings - Fork 1.1k
build: fall back to previous image version on release PRs #12848
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 4 commits
Commits
Show all changes
16 commits
Select commit
Hold shift + click to select a range
3c59412
build: fall back to previous image version on release PRs
meltsufin 5fa7830
build: extract image name to variable in hermetic script
meltsufin 823b98c
build: improve robustness of fallback version extraction
meltsufin c1395d2
build: prevent script termination on empty fallback match
meltsufin 53d67a1
refactor: centralize generator docker execution and fallback logic
meltsufin 16cfa1b
refactor: extract fallback tag from versions.txt instead of workflow …
meltsufin ef92609
refactor: remove unused gapic_generator_version from generation_confi…
meltsufin 54269dc
fix: use remote ref origin/ for fallback tag extraction in CI
meltsufin b74fe50
Merge branch 'main' into release-please--fix-12825
meltsufin 1ae26cc
fix: fetch target branch to get fallback tag in CI
meltsufin d19bfbb
Merge branch 'release-please--fix-12825' of github.com:googleapis/goo…
meltsufin 43835e2
impl: add GENERATOR_VERSION to final stage of Dockerfile
meltsufin 68519fb
chore: pass GENERATOR_VERSION to validation container in CI
meltsufin 2cbaa3c
chore: pass GENERATOR_VERSION to hermetic_library_generation workflow
meltsufin 7dc57e7
chore: generate libraries at Tue Apr 21 11:18:32 UTC 2026
cloud-java-bot d07cfd9
Merge branch 'main' into release-please--fix-12825
meltsufin File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could create release-please PRs from CLI as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's fine, as long as the branch prefix is
release-please--.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
But that means we have to remember using
release-please--as the branch name, is there any harm we do this for every branches?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You shouldn't have to use the Release Please CLI going forward which should eliminate the need to remember the branch prefix. The risk of always falling back is that if someone configures and invalid generator version, they won't get a CI failure as feedback.