chore(deps): update homebrew/actions digest to 3b81d43 - #1101
chore(deps): update homebrew/actions digest to 3b81d43#1101mergeraptor[bot] wants to merge 2 commits into
Conversation
Signed-off-by: sec-check[bot] <sec-check[bot]@users.noreply.github.com>
Edited/Blocked NotificationRenovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR. You can manually request rebase by checking the rebase/retry box above. |
hanthor
left a comment
There was a problem hiding this comment.
Diff is fine; it's stuck because no check has reported on the current head
The change itself is a clean one-line SHA-pinned digest bump and it merges into current main without conflict:
$ git merge-tree --write-tree main pr1101 # no conflict
- uses: Homebrew/actions/setup-homebrew@c722b5d961eb7f3ebec81ec2e5584faf7c3cff5d # main
+ uses: Homebrew/actions/setup-homebrew@3b81d438eda92ee13b5849940d993be027717ecf # mainStill SHA-pinned with the # main comment intact, so the supply-chain posture is unchanged. Only .github/workflows/validate-brewfiles.yaml is touched — nothing under system_files/, so no image blast radius.
Why it isn't merging: mergeable_state is blocked and there are zero reported checks on head 905cd33:
$ pull_request_read get_status 1101
{"state":"pending","sha":"905cd33...","total_count":0,"statuses":[]}
$ pull_request_read get_check_runs 1101
{"total_count":0,"check_runs":[]}
The automerge label can't fire while required checks are pending-and-absent, so this will sit indefinitely without a nudge.
Two contributing details worth a maintainer's eye:
- There is a second, non-Renovate commit on this branch.
905cd33 ci: retry transient failing checkssits on top ofcaeb02c chore(deps): update homebrew/actions digest to 3b81d43. Renovate treats a branch with commits it didn't author as modified and generally stops rebasing it, which means this PR will also not self-update asmainmoves (its base isdff365d;mainis now56d81ef). If that commit was only meant to re-trigger CI, the cleaner path is ticking the rebase checkbox in the PR body and letting Renovate recreate the branch. - The workflow this edits is path-filtered, so pushing an unrelated empty-ish commit is not a reliable way to re-trigger it. A
workflow_dispatch/ re-run from the Actions tab is more likely to produce the missing check.
Nothing here needs changing in the diff — it just needs a check to actually run.
Generated by Claude Code
castrojo
left a comment
There was a problem hiding this comment.
LGTM, clean SHA digest bump passing all checks
This PR contains the following updates:
c722b5d→3b81d43Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Configuration
📅 Schedule: (UTC)
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate CLI.