Skip to content

ci: pin goreleaser-action back to allowlisted v7.2.3 - #108

Merged
sethsec merged 1 commit into
mainfrom
fix/goreleaser-action-allowlist
Oct 20, 2026
Merged

sethsec merged 1 commit into
mainfrom
fix/goreleaser-action-allowlist

Conversation

@sethsec

@sethsec sethsec commented Oct 20, 2026

Copy link
Copy Markdown
Collaborator

Why

Tagging v1.0.0 triggered the Release workflow, which failed at startup (startup_failure, 0 jobs scheduled, no release built).

Root cause: this repo enforces a SHA-pinned allowed-actions policy:

  • allowed_actions: selected, sha_pinning_required: true, github_owned_allowed: true
  • goreleaser allowlist entry is only goreleaser/goreleaser-action@f06c13b… (v7.2.3)

Dependabot PR #106 bumped goreleaser-action to v7.3.0 (a4f02ab…), which is not in the allowlist, so GitHub blocks the run before it starts. (CodeQL's SHA bump in the same PR was fine because GitHub-owned actions are exempt.)

Fix

Revert just the goreleaser-action line back to the vetted, allowlisted v7.2.3 SHA. The AWS SDK and codeql-action bumps from #106 are untouched.

To adopt v7.3.0 later, add its SHA to the repo Actions allowlist first, then bump.

🤖 Generated with Claude Code

Dependabot PR #106 bumped goreleaser-action to v7.3.0, but this repo
enforces a SHA-pinned allowed-actions policy (sha_pinning_required=true)
whose allowlist contains only the v7.2.3 SHA for goreleaser-action. The
v7.3.0 SHA is not allowlisted, so the tag-triggered Release workflow
fails at startup (startup_failure, no jobs scheduled) and never builds a
release. GitHub-owned actions like codeql-action are exempt, which is why
that bump was fine.

Revert just this line to the vetted, allowlisted SHA so releases work. To
adopt v7.3.0 later, add its SHA to the repo's Actions allowlist first,
then bump.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
@sethsec
sethsec merged commit a335cb5 into main Oct 20, 2026
10 checks passed
@sethsec
sethsec deleted the fix/goreleaser-action-allowlist branch October 20, 2026 18:02
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant