Skip to content

CI failure: Homebrew/actions/setup-homebrew@master no longer resolves (pin to release SHA) #416

Description

@claude

Summary

Smoke Test CI (smoke.yml) is failing at the Set up job step of the Linters job with:

##[error]Unable to resolve action `homebrew/actions@master`, unable to find version `master`

This is not caused by the PR #415 changes (that PR only touches private_dot_config/just/plugins.just). main is broken by the same root cause — the first failing run on main was 34711952332 (commit caf1566, 2026-09-12).

Root cause

Homebrew deprecated the Homebrew/actions/setup-homebrew@master ref. The 2026-09-12 run (which still resolved @master) logged the deprecation notice:

Homebrew/actions/setup-homebrew@master is deprecated. Please update your workflow references to pin Homebrew/actions/setup-homebrew@1f8e202ffddf94def7f42f6fa3a482e821489f9c (2026.07.10.1). The "master" branch sync will stop and this warning will become an error when Homebrew 5.2.0 is released (no earlier than 2026-06-10).

By the 2026-09-13 run the master branch sync had stopped, so the ref no longer resolves and the warning became a hard Set up job error.

Why this bot could not auto-fix it

I prepared the fix, but the push was rejected because the GitHub App token lacks the workflows permission:

refusing to allow a GitHub App to create or update workflow `.github/workflows/smoke.yml`
without `workflows` permission

So this needs a human (or a token with workflows scope) to apply.

Suggested fix

Pin every setup-homebrew@master reference to the release SHA Homebrew recommends (SHA 1f8e202ffddf94def7f42f6fa3a482e821489f9c, tag 2026.07.10.1):

uses: Homebrew/actions/setup-homebrew@1f8e202ffddf94def7f42f6fa3a482e821489f9c

(Add a trailing # 2026.07.10.1 comment on that line for readability.)

Affected files (all use @master):

  • .github/workflows/smoke.yml (lines 31 and 57) — the failing workflow
  • .github/workflows/sbom.yml (line 30)
  • .github/workflows/coverage.yml (line 29)
  • .github/workflows/claude.yml (line 71)

Pinning to a SHA (rather than master or main) is also the recommended practice for third-party actions in a public repo.

Suggested labels: bug, ci-failure.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions