build: add cab-token-generator to always install deps#12851
Open
build: add cab-token-generator to always install deps#12851
Conversation
Adds 'google-auth-library-java/cab-token-generator' to the `always_install_deps_list` in `.kokoro/common.sh`. After the monorepo migration, release PRs failed the `gapic-generator-java-bom` check because they couldn't resolve the new auth library version from Maven Central before it was published. This fix ensures the artifact is installed to the local Maven repository during the CI's install phase, satisfying the canary validation without requiring a full repository build. Fixes #12843
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.
Adds 'google-auth-library-java/cab-token-generator' to the
always_install_deps_listin.kokoro/common.sh.After the monorepo migration, release PRs failed the
gapic-generator-java-bomcheck because they couldn't resolve the new auth library version from Maven Central before it was published.This fix ensures the artifact is installed to the local Maven repository during the CI's install phase, satisfying the canary validation without requiring a full repository build.
Fixes #12843