githubnext / githubnext/gh-aw-cao
[aw-maintenance:failures-investigator] Blocked compile-agentic version v0.82.13 blocks all activation jobs
- Dominant language
- JavaScript
- Stars
- 3
- Forks
- 1
- Avg merge
- 48m
- Merged PRs (30d)
- 853
Description
**Target repository**: `githubnext/gh-aw-workshop`
### Problem
Every agentic workflow's `activation` job fails at the `Check compile-agentic version` step with:
```
##[error]Blocked compile-agentic version: v0.82.13 is in the blocked versions list. Update gh-aw to the latest version and recompile your workflow.
```
This blocks 100% of workflow runs in the repository during the analysis window (43 failed runs across the last 24 hours), confirmed across at least 3 distinct workflows (Workshop Builder, Workflow Skills Editor, Workshop Link Checker).
### Affected runs
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33810480125
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33807856135
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33807178518
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33805019420
- https://github.com/githubnext/gh-aw-workshop/actions/runs/33799237747
### Probable root cause
The compiled lock files in `githubnext/gh-aw-workshop` embed `GH_AW_COMPILED_VERSION: v0.82.13`. The activation job's `Check compile-agentic version` step fetches `https://raw.githubusercontent.com/github/gh-aw-actions/main/.github/aw/compat.json` and rejects runs whose compiled version is on the blocked-versions list. `v0.82.13` is currently blocked, so the check hard-fails the activation job for every workflow compiled with that version, before the agent task itself ever runs.
### Proposed remediation
1. Upgrade the `gh-aw` extension/CLI used to compile workflows in this repository to a version newer than the blocked `v0.82.13` (check `gh extension upgrade aw` or the pinned version in CI tooling).
2. Re-run `gh aw compile` for all `.github/workflows/*.md` sources so every `.lock.yml` embeds an unblocked `GH_AW_COMPILED_VERSION`.
3. Commit the regenerated lock files in one PR.
### Success criteria
- The `activation` job's `Check compile-agentic version` step passes (no `##[error]Blocked compile-agentic version` message) on the next scheduled/dispatched run of each previously-failing workflow.
- All `.lock.yml` files in the repository report a `GH_AW_COMPILED_VERSION` that is not present in the current blocked-versions list.
### Control Plane
- Correlation ID: `33814131545-73`
- Central repository: `githubnext/gh-aw-cao`
- Control plane run: https://github.com/githubnext/gh-aw-cao/actions/runs/33814131545
> Generated by [:rotating_light: AW Maintenance / Failures](https://github.com/githubnext/gh-aw-cao/actions/runs/33814131545) · copilot · auto · 30.4 AIC · ⌖ 8.27 AIC · ⊞ 14.9K · [◷](https://github.com/search?q=repo%3Agithubnext%2Fgh-aw-cao+is%3Aissue+%22gh-aw-workflow-call-id%3A+githubnext%2Fgh-aw-cao%2Faw-failures-investigator%22&type=issues)
> - [x] expires on Sep 17, 2026, 10:47 PM UTC
Contributor guide
Research direction
Start with the `.github/workflows/*.md` sources and their generated `.lock.yml` files, then check the repository's `gh-aw` version using `gh extension upgrade aw` or the pinned CI tooling. Run `gh aw compile` for each workflow and inspect the embedded `GH_AW_COMPILED_VERSION`. Done means all lock files use an unblocked version and the activation checks pass on subsequent runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 72/100