Skip to content

[P8.1] Recompile triage-incoming-issues.lock.yml to pick up gh-aw v0.79.8 + checkout v6.0.3 #327

Open

Description

@frankbria

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:

  1. Update the local gh-aw extension to v0.79.8 (gh extension upgrade aw or equivalent).
  2. Recompile the source workflow: gh aw compile (regenerates triage-incoming-issues.lock.yml with the matching setup pin and compiler_version metadata).
  3. The recompile will also naturally pick up actions/checkout 6.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.)
  4. Verify guards pass: bats tests/unit/test_workflow_sha_pinning.bats.
  5. Heads-up: committing a recompiled .lock.yml may 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

Activity

  1. coderabbitai commented on Jun 15, 2026

    @coderabbitai
    Contributor
    🔗 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 plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  2. github-actions commented on Jun 15, 2026

    @github-actions

    🏷️ Triage: maintenance / infrastructure chore

    Thanks for the detailed write-up. Here's how this issue categorizes:

    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):

    1. Upgrade the gh-aw extension to v0.79.8 and recompile with gh aw compile — do not hand-edit the setup pin.
    2. Confirm guards pass: bats tests/unit/test_workflow_sha_pinning.bats.
    3. After this lands, close Dependabot PR ci(deps): bump the github-actions group with 3 updates #309 as superseded by ci(deps): bump claude-code-action to v1.0.148; fix gh-aw dependabot ignore #326 + this issue.

    No automated action taken beyond this triage note.

    Generated by Issue Triage Assistant for issue #327 · opus48 597.8K · ◷

  3. changed the title [-]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[/+] on Jun 15, 2026
  4. frankbria commented on Nov 4, 2026

    @frankbria
    OwnerAuthor

    #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.

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

    dependenciesPull requests that update a dependency fileinfrastructureBuild/tooling infrastructureneeds-triageNeeds maintainer review against the v2 direction

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions