Skip to content

Recompile lock files with gh-aw v0.71.1 release - #239

Merged
mrjf merged 1 commit into
mainfrom
fix/recompile-with-v0.71.1-release
Apr 29, 2026
Merged

Recompile lock files with gh-aw v0.71.1 release#239
mrjf merged 1 commit into
mainfrom
fix/recompile-with-v0.71.1-release

Conversation

@mrjf

@mrjf mrjf commented Apr 29, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Recompile both lock files with gh aw v0.71.1 (the latest release) instead of the dev build from main
  • Remove max-patch-files: 500 from autoloop.md (not supported in v0.71.1 schema)

Problem

The lock files were compiled with a dev build of gh-aw main, which emits uses: ./actions/setup (local action references that only work inside the gh-aw repo). Consumer repos don't have actions/setup/action.yml, so every workflow fails at activation:

Can't find 'action.yml' under 'actions/setup'

Both Autoloop and Evergreen have been broken since the upgrade.

Fix

Recompiling with the v0.71.1 release restores remote action references (github/gh-aw-actions/setup@sha).

Test plan

  • Merge and verify the next scheduled Autoloop run passes the activation step
  • Verify Evergreen runs pass activation

🤖 Generated with Claude Code

…files

The lock files were compiled with a dev build of gh-aw (main branch) which
emitted `uses: ./actions/setup` (local action references). This only works
inside the gh-aw repo itself — consumer repos like tsessebe don't have
`actions/setup/action.yml`, causing every workflow to fail at activation:

  Can't find 'action.yml' under '/home/runner/work/tsessebe/tsessebe/actions/setup'

Recompiling with the v0.71.1 release restores the remote action references
(`github/gh-aw-actions/setup@sha`). Also removes `max-patch-files: 500`
from autoloop.md since v0.71.1 doesn't support that schema field.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@mrjf
mrjf merged commit 1958b42 into main Apr 29, 2026
11 checks passed
@mrjf
mrjf deleted the fix/recompile-with-v0.71.1-release branch April 29, 2026 04:42
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