chore(main): release 6.7.2 - #457
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
July 30, 2026 13:08
2bbfa17 to
a473c54
Compare
Contributor
Author
|
🤖 Created releases: 🌻 |
4 tasks
sebastiancorrea81
added a commit
that referenced
this pull request
Aug 7, 2026
…ll_request (#479) ## Problem `auto-merge-release-pr` (triggered on `pull_request`) has been silently broken for a while: the release-please PR is always opened by `github-actions[bot]`, whose `author_association` on this repo is `CONTRIBUTOR` (not `MEMBER`/`COLLABORATOR`). That's enough for GitHub's "require approval for outside collaborators" gate to treat its `pull_request`-triggered runs as needing manual approval — the same mechanism used for fork PRs — even though this branch (`release-please--branches--main`) lives in this repo, not a fork. Evidence: - Every recent release PR (#472/6.8.2, #464/6.8.1, #460/6.8.0, #457/6.7.2, #453/6.7.1) was merged **by a human**, never by the bot. - The last two `auto-merge-release-pr` runs on PR #476 (release 6.9.0) completed with conclusion `action_required` and **zero jobs executed**. - An earlier run on the same branch was stuck `queued` for >21h and never ran. ## Fix Switch the trigger from `pull_request` to `workflow_run` (on `"Release Please"` completing). Runs triggered by `workflow_run` always use the workflow file from the default branch with full permissions and aren't subject to the outside-collaborator approval gate. Since `workflow_run` doesn't carry PR context, a new `find-pr` job resolves the open release PR itself (same lookup `generate-readmes` already does in `release.yml`) and validates its author/label before merging — this is exactly what the reusable workflow's existing `pr_number` input was already built for (see its description in `nullplatform/actions-nullplatform`), so **no changes needed there**. This also removes the `concurrency`/`cancel-in-progress` workaround for the `generate-readmes` follow-up commit race — `workflow_run` only fires once the entire "Release Please" run (both jobs) has finished, so there's nothing to race against anymore. ## Test plan - [ ] Merge this PR. - [ ] Merge (or wait for) the next normal feature/fix PR to `main`. - [ ] Confirm in the Actions tab that `auto-merge-release-pr` now fires via `workflow_run`, `find-pr` resolves the release PR, and `automerge` completes successfully (no `action_required`/`queued`). - [ ] Confirm the release PR gets merged by the bot without human intervention, and the tag/GitHub Release is published automatically. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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
1 participant
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.
🤖 I have created a release beep boop
6.7.2 (2026-07-30)
Bug Fixes
This PR was generated with Release Please. See documentation.