-
Notifications
You must be signed in to change notification settings - Fork 604
Exclude protolite well known types from version bump. #6909
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
base: main
Are you sure you want to change the base?
Conversation
📝 PRs merging into main branchOur main branch should always be in a releasable state. If you are working on a larger change, or if you don't want this change to see the light of the day just yet, consider using a feature branch first, and only merge into the main branch when the code complete and ready to be released. |
Vertex AI Mock Responses Check
|
Test Results 1 016 files + 1 016 1 016 suites +1 016 34m 28s ⏱️ + 34m 28s For more details on these failures, see this check. Results for commit 3441850. ± Comparison against base commit 4fb4dfd. ♻️ This comment has been updated with latest results. |
Coverage Report 1Affected Products
Test Logs |
Per b/413403910,
This adds filtering logic to not bump the version of
protolite-well-known-types
when it releases. This solves the issue of theversion
andlatestReleasedVersion
not aligning (which must be enforced due to b/285892320).More specifically, this PR adds a toggle for the default
bump
behavior inVersionBumpTask
. We then set this tofalse
when the project'sartifactId
isprotolite-well-known-types
.This allows us to still [automatically] update the
latestReleasedVersion
(should we ever release well known types again), without bumping theversion
.The
VersionBumpTask
docs have been updated to accommodate this.