chore(ci): use YOSHI_CODE_BOT_TOKEN for tag generator workflow - #1344
Merged
suztomo merged 1 commit intoSep 4, 2026
Merged
Conversation
Revert googleapis#1321 now that yoshi-code-bot account permissions have been configured in the repository. Using YOSHI_CODE_BOT_TOKEN allows release tags pushed by the workflow to trigger downstream release workflows, which are otherwise suppressed when pushed with GITHUB_TOKEN.
suztomo
marked this pull request as ready for review
September 4, 2026 19:50
suztomo
enabled auto-merge (squash)
September 4, 2026 19:51
aandreassa
approved these changes
Sep 4, 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.
Summary
Let's use
YOSHI_CODE_BOT_TOKENinstead ofGITHUB_TOKENfor the tag generator release workflow now that repository permissions foryoshi-code-bothave been configured.Context & Motivation
YOSHI_CODE_BOT_TOKENso that release tags pushed by the workflow could trigger downstream release workflows (which GitHub Actions restricts when using the defaultGITHUB_TOKEN).GITHUB_TOKENbecauseyoshi-code-botlacked write permissions at the time and failed with HTTP 403.yoshi-code-bothave now been configured, enabling the workflow to useYOSHI_CODE_BOT_TOKENas originally intended.