Skip to content

fix(release): repoint 6 orphaned gha-release-* action pins crashing Dependabot#336

Merged
jdfalk merged 1 commit into
mainfrom
fix/dependabot-orphaned-action-pins
Jul 21, 2026
Merged

fix(release): repoint 6 orphaned gha-release-* action pins crashing Dependabot#336
jdfalk merged 1 commit into
mainfrom
fix/dependabot-orphaned-action-pins

Conversation

@jdfalk

@jdfalk jdfalk commented Jul 21, 2026

Copy link
Copy Markdown
Collaborator

Root cause (this is why Dependabot stopped opening PRs)

Diagnosed from the Dependabot dynamic run logs (visible in Actions as dynamic events — thanks to that pointer). Job job_1471642895 (github_actions in /. - Update) crashed:

ERROR Error processing falkcorp/gha-release-python (HelperSubprocessFailed)
error: no such commit f3105cab8ecca34051c16c989cc809b19ae5a297
  ...GithubActions...find_container_branch / latest_commit_for_pinned_ref

reusable-release.yml pinned six first-party actions to commit SHAs labelled # v2.0.x / # v1.2.0tags that were never published (all 404). Those commits are unreachable from any tag, so Dependabot's github_actions updater crashes trying to resolve them. Because github_actions is part of the multi-ecosystem-group: dependencies, that single crash blocks the entire grouped version-update PR — which is why zero version-update PRs have been created since 2026-06-04 (#289).

GitHub Actions itself tolerates the orphaned SHAs (it fetches the exact commit), so releases kept working — only Dependabot choked, silently.

Fix

Repoint each to its latest real release:

Action Was (phantom) Now
gha-release-python # v2.0.0 a6acf4ec # v1.0.3
gha-release-docker # v2.0.0 f2775359 # v1.0.3
gha-release-go # v2.0.1 cf4aea67 # v1.0.3
gha-release-rust # v2.0.0 9cdb217e # v1.0.3
gha-release-frontend # v2.0.0 731cf92c # v1.0.3
gha-package-assets # v1.2.0 a55b9a19 # v1.1.5

Not a downgrade — those v2 tags never existed; v1.0.3 / v1.1.5 are each action's current latest release (chronologically newer than the orphaned SHAs).

The remaining stale-but-valid pins (protobuf, detect-languages, docs-generator) point to real tags and will be bumped by Dependabot itself once this unblocks it.

🤖 Generated with Claude Code

…ependabot

reusable-release.yml pinned gha-release-python/docker/go/rust/frontend and
gha-package-assets to SHAs labelled v2.0.x / v1.2.0 — tags that were never
published. Those commits are unreachable from any tag, so Dependabot's
github_actions updater crashed ("no such commit ...") on the first one
(gha-release-python@f3105cab). Because github_actions is part of the
multi-ecosystem-group "dependencies", that crash blocked ALL grouped
version-update PRs — none created since 2026-06-04. Repinned each to its
latest real release (v1.0.3, package-assets v1.1.5).

Diagnosed from the Dependabot dynamic run logs (job_1471642895).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013vU67T2LJDCbYTBs9ZFAf2
@jdfalk
jdfalk merged commit 17132a6 into main Jul 21, 2026
23 of 29 checks passed
@jdfalk
jdfalk deleted the fix/dependabot-orphaned-action-pins branch July 21, 2026 17:27
jdfalk added a commit that referenced this pull request Jul 21, 2026
…ot-firewall

The pip entry only scanned '/', so scripts/requirements-notifications.txt and
scripts/copilot-firewall/requirements.txt got no update PRs (the latter's Pygments
alert had no path to a fix). Switched directory:/ to a directories list covering
all three tracked pip manifests. Also forces a fresh Dependabot re-registration,
confirming the github_actions job no longer crashes after #336.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013vU67T2LJDCbYTBs9ZFAf2
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