Repository navigation
Open
Labels
dependenciesPull requests that update a dependency filePull requests that update a dependency fileinfrastructureBuild/tooling infrastructureBuild/tooling infrastructureneeds-triageNeeds maintainer review against the v2 directionNeeds maintainer review against the v2 direction
Description
Background
Dependabot PR #309 (github-actions group) tried to bump three actions. PR #326 took the two safe ones (anthropics/claude-code-action → v1.0.148, plus a fix to the gh-aw Dependabot ignore glob). This issue tracks the part that cannot be done by bumping a pin: the compiled gh-aw lock file.
What needs to happen
.github/workflows/triage-incoming-issues.lock.yml is a compiled artifact. Its github/gh-aw-actions/setup pin is version-locked to the gh-aw compiler that generated it (currently v0.77.5). Dependabot's attempt to bump it to v0.79.8 desynced the runtime .cjs scripts from the compiled body and tripped the guard:
not ok 995 gh-aw lock files keep setup pins at the compiler version
triage-incoming-issues.lock.yml [compiler v0.77.5]:
uses: github/gh-aw-actions/setup@c0338fe… # v0.79.8
Fix by recompiling ('gh aw compile'), never by bumping the pin.
The fix is to upgrade the gh-aw toolchain and recompile, not to hand-edit the pin:
- Update the local gh-aw extension to v0.79.8 (
gh extension upgrade awor equivalent). - Recompile the source workflow:
gh aw compile(regeneratestriage-incoming-issues.lock.ymlwith the matchingsetuppin andcompiler_versionmetadata). - The recompile will also naturally pick up
actions/checkout6.0.2 → 6.0.3 inside the lock file — its only remaining 6.0.2 reference. (The hand-maintained workflows are already on 6.0.3.) - Verify guards pass:
bats tests/unit/test_workflow_sha_pinning.bats. - Heads-up: committing a recompiled
.lock.ymlmay trip the local pre-commit secret scanner on the manifest line (names + SHAs, not values) — verify there are no real secrets, then commit (see prior gh-aw recompile PRs).
Notes
- Do not simply bump the pin — the guard exists precisely to prevent that desync (Issue Upgrade gh-aw extension and recompile triage-incoming-issues.lock.yml (currently version-locked at v0.46.5) #287, PR chore(deps): bump the github-actions group across 1 directory with 7 updates #283).
- With PR ci(deps): bump claude-code-action to v1.0.148; fix gh-aw dependabot ignore #326's ignore-glob fix in place, Dependabot should stop re-proposing this bump.
- Once this lands, Dependabot PR ci(deps): bump the github-actions group with 3 updates #309 can be closed (superseded by ci(deps): bump claude-code-action to v1.0.148; fix gh-aw dependabot ignore #326 + this issue).
Reacted by coderabbitai
Metadata
Metadata
Assignees
Labels
dependenciesPull requests that update a dependency filePull requests that update a dependency fileinfrastructureBuild/tooling infrastructureBuild/tooling infrastructureneeds-triageNeeds maintainer review against the v2 directionNeeds maintainer review against the v2 direction
Activity
coderabbitai commentedon Jun 15, 2026
🔗 Related PRs
#281 - ci(workflows): pin GitHub Actions to commit SHAs (
#275) [merged]#288 - ci(workflows): recompile triage workflow with gh-aw v0.77.5 (
#287) [merged]#292 - fix(triage): switch issue-triage workflow to Claude engine (
#272,#290) [merged]#308 - feat(ci): publish ralph-sandbox image to GHCR on release tags (
#298) [merged]#326 - ci(deps): bump claude-code-action to v1.0.148; fix gh-aw dependabot ignore [closed]
📝 Issue Planner
Check the box below or use the
@coderabbitai plancommand to generate an implementation plan and prompts that you can use with your favorite coding assistant.🧪 Issue enrichment is currently in open beta.
To disable automatic issue enrichment, add the following to your
.coderabbit.yaml:💬 Have feedback or questions? Drop into our discord!
github-actions commentedon Jun 15, 2026
🏷️ Triage: maintenance / infrastructure chore
Thanks for the detailed write-up. Here's how this issue categorizes:
v0.79.8toolchain +actions/checkout6.0.3). This is intentional maintenance, not a bug — thetest_workflow_sha_pinning.batsguard tripping is the correct, intended behavior protecting against a runtime.cjs↔ compiled-body desync, exactly as designed in Upgrade gh-aw extension and recompile triage-incoming-issues.lock.yml (currently version-locked at v0.46.5) #287 / chore(deps): bump the github-actions group across 1 directory with 7 updates #283.Labels: already correctly tagged
infrastructure+dependencies; no triage label change needed. None of the auto-triage labels (bug/enhancement/needs-info/documentation) apply to a chore like this, so I'm intentionally not adding one.Recommended next steps (per the issue body):
v0.79.8and recompile withgh aw compile— do not hand-edit thesetuppin.bats tests/unit/test_workflow_sha_pinning.bats.No automated action taken beyond this triage note.
ci(deps): bump claude-code-action to v1.0.148; fix gh-aw dependabot i…
[-]Recompile triage-incoming-issues.lock.yml to pick up gh-aw v0.79.8 + checkout v6.0.3[/-][+][P8.1] Recompile triage-incoming-issues.lock.yml to pick up gh-aw v0.79.8 + checkout v6.0.3[/+]docs(plan): record R.2 true open-work list (multi-provider epic)
docs(status): reconcile to v0.11.5
test(agents): registry/adapter parity guard (frankbria#327 MP.15a)
ci(deps): keep gh-aw lock file compiler-managed
ci(deps): bump the github-actions group across 1 directory with 11 up…
frankbria commentedon Nov 4, 2026
#386 updated the hand-maintained workflows to checkout v7.0.1, setup-node v7.1.0, upload-artifact v7.0.2 and download-artifact v8.0.2. The lock file was deliberately left on its compiler-managed pins. The recompile will pick its own pins. If it doesn't land on checkout v7, note that v7 blocks fork-PR checkout under pull_request_target and workflow_run, which shouldn't affect this issues-triggered workflow.