Repository navigation
chore: remove unused release-freeze and release-unfreeze workflows - #28296
Merged
Merged
Conversation
The "Freeze releases" and "Unfreeze releases" workflows toggle FREEZE_RELEASES in .kokoro/release-generated.sh, but the weekly release of the generated google-apis-* gems no longer runs that script, so they don't freeze or unfreeze anything. Remove them to avoid confusion. Release freezes for these gems are now handled in the release infrastructure.
zhumin8
changed the title
zhumin8
force-pushed
the
remove-release-freeze-workflow
branch
from
October 21, 2026 20:10
6c6e7eb to
574f226
Compare
torreypayne
approved these changes
Oct 21, 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
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.
The "Freeze releases" and "Unfreeze releases" workflows toggle
FREEZE_RELEASES in .kokoro/release-generated.sh, but the weekly release of
the generated google-apis-* gems no longer runs that script, so they don't
freeze or unfreeze anything. Remove them to avoid confusion. Release freezes
for these gems are now handled in the release infrastructure.