fix: switch auto-merge-release-pr to pull_request trigger - #455
Merged
Conversation
…flow_run The workflow_run-triggered version merged in #454 fails immediately with startup_failure (0 jobs ever scheduled) for reasons that aren't visible via the API — likely an org-level Actions policy restricting workflow_run, but that needs admin access to confirm. Switch back to the pull_request trigger proven to work in the other services-* repos, and instead solve the generate-readmes race with concurrency: cancel-in-progress keyed on the PR number. When the README-regeneration commit lands (observed ~38s after the release PR is opened, on a real release), it fires a new 'synchronize' event; GitHub cancels whatever older run for the same PR is still waiting on checks, so only the run for the final commit can ever reach the merge step.
agustincelentano
approved these changes
Jul 30, 2026
sebastiancorrea81
added a commit
that referenced
this pull request
Jul 30, 2026
🤖 I have created a release *beep* *boop* --- ## [6.7.2](v6.7.1...v6.7.2) (2026-07-30) ### Bug Fixes * allow gateway egress to additional VPC CIDR blocks ([#452](#452)) ([c6a9f3a](c6a9f3a)) * use pull_request trigger with per-PR concurrency instead of workflow_run ([#455](#455)) ([6475fb6](6475fb6)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please).
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
2 participants
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
Supersedes #454. That workflow_run-triggered version fails with
startup_failurein practice (confirmed on main after merge — 0 jobs scheduled, no further detail available via the API; possibly an org Actions policy restrictingworkflow_run, but I don't have the access to confirm).Reverts to the
pull_requesttrigger already proven working in nullplatform/services-postgresql-rds and the otherservices-*repos, and instead handles thegenerate-readmesrace withconcurrency: cancel-in-progresskeyed on the PR number:synchronizeevent → a fresh run starts for the samegroup:.Test plan