Repository navigation
feat(dev): expand release:verify with docs, check runs, and release-verify workflow - #9789
Merged
Merged
Conversation
bshaffer
changed the title
bshaffer
marked this pull request as draft
October 14, 2026 15:22
bshaffer
changed the title
bshaffer
changed the title
…ne issue per release
…eleaseVerifyCommand
…and GitHub and simplify release-verify.yaml
|
The PR LGTM. I see that we'll be removing |
jinseopkim0
self-requested a review
October 15, 2026 20:53
jinseopkim0
approved these changes
Oct 15, 2026
bshaffer
changed the title
…its-cron-audit # Conflicts: # .github/workflows/release.yml
bshaffer
marked this pull request as ready for review
October 16, 2026 17:53
…dit' into chore/remove-postsubmits-cron-audit
Hectorhammett
approved these changes
Oct 30, 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.
Expand
./dev/google-cloud release:verifyto run daily in order to verify the following for the latest releases: 1) postsubmits passed, 2) all packages were released, and 3) all docs were published. Once this is done, it updates the GitHub Release with a verification table.release:verifywith[tag]argument,-t/--tokenand--update-releasePENDINGgrace period to deploy before being marked as failedPost-Submit ChecksandComponent Releasesverification tables on the GitHub Release body (and ignore them inReleaseNotes::parseChangelog()).github/workflows/release-verify.yamlto verify unverified releases from the last 14 days daily and open an issue on failure