chore(main): release 7.1.1 - #163
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
September 17, 2026 12:22
d6b4342 to
cfe9163
Compare
mogita
added a commit
that referenced
this pull request
Sep 17, 2026
The github.actor clause made the skip miss the path CONTRIBUTING tells maintainers to take. With strict: true the Release PR has to be brought up to date whenever main moves, and Update branch attributes that merge commit to the person who clicked, so github.actor is a human and the guard fell through to running the full suite. Verified on #163: 8c31d76 is exactly that merge, and its run had actor=mogita and spent 3m51s on the 1.19 integration leg. Dropping the clause fires the skip on both Update branch and Approve and run. The remaining three clauses still cannot be forged: a PR author cannot be set to github-actions[bot], and the head repository must be this one. The cost is that a human commit pushed onto a Release PR is no longer tested here. release.yml calls this same workflow against the merge commit before it tags, which is what actually gates the release, and a `run-tests` label now forces the suite on any Release PR, since a re-run keeps the original actor and neither workflow has a dispatch trigger. Also corrects two comments. The claim that lint.yml and reviewdog.yml compile version.go was wrong on both counts: lint.yml only runs `go mod tidy`, and reviewdog.yml pipes golangci-lint into reviewdog under `bash -e` without pipefail, so the job takes reviewdog's exit status and its default -fail-level=none returns 0. And the note that a job-level `if:` is evaluated before the matrix expands is restored, because it is the only record of why re-adding the six required contexts would block every Release PR forever.
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
2 times, most recently
from
September 24, 2026 09:09
fd46666 to
b745cd2
Compare
github-actions
Bot
force-pushed
the
release-please--branches--main
branch
from
September 25, 2026 10:45
b745cd2 to
0b1e4ee
Compare
This branch was successfully deployed
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
7.1.1 (2026-09-25)
Bug Fixes
This PR was generated with Release Please. See documentation.