Repository navigation
Advisory reviewer: examples pin a nonexistent @v1, and v0.2.1's pinned harnesses refuse current models #475
Description
Found while enabling the advisory reviewer on a lab repo (2026-10-03).
1. examples/review.yml references a tag that doesn't exist
examples/review.ymlusesouterloop-science/outerloop/.github/workflows/advisory-review-agent.yml@v1. There is nov1tag; the tags are v0.1.0 … v0.2.1 and v0.3.0rc1.docs/install.mduses@main.- Copying the example makes every run fail at workflow resolution ("This run likely failed because of a workflow file issue"), which looks like a configuration error rather than a missing ref. At least one other lab repo copied the example and has never had a working reviewer.
2. v0.2.1's pinned harness versions reject current models (both rounds were posted as outerloop:round-skipped)
backend: claudewithmodel: claude-opus-5-5fails withAPI Error: 400 Claude Code 2.1.229 does not support this model; version 2.1.280 or newer is required.backend: codexwithmodel: gpt-5.6-terraworked for several rounds on 2026-10-03, then started refusing:RuntimeError: run outerloop harness upgrade codex. v0.2.1 installs@openai/codex@0.130.0(advisory-review-agent.ymlline 192).
Ask
- Publish a moving
v1tag, or a stable release whose pins work with current models, and pointexamples/review.ymlat it. Alternatively, change the example to@mainuntilv1exists. - Ideally the skip comment would name the pinned harness version and the minimum version required, so users can tell "upgrade the reusable workflow ref" apart from an API outage.
Workaround meanwhile: pin @main (the version-pin reader from v0.3.0rc1).
Activity
renmengye commentedon Oct 4, 2026
Update: pinning the reusable workflow to
main(b749775) doesn't fix part 2. It installs@openai/codex@0.160.0via the pin reader, and the codex round still fails withagent review produced no verdict … run outerloop harness upgrade codex(gpt-5.6-terra, 2026-10-04 02:10 UTC). So main's codex pin is also behind what the model requires.renmengye commentedon Oct 4, 2026
Thanks. Status:
@v1in the example: fixed in Codex host check: npm's script launcher finds its own vendored host #476. The example now uses@mainwith a note to pin a release tag or SHA (andreviewer_ref) in production. A movingv1tag is a release-policy decision; it fits best once 0.3.0 is final.@v0.2.1installed Codex 0.130.0, while the defaultreviewer_ref: maincheckout pinned 0.160.0 and asked for an upgrade. On@mainthe workflow reads the pins from the same checkout, so they agree. Install Codex's code-mode host beside the pinned binary #473 (merged) adds Codex 0.160's code-mode host for native installs, and Codex host check: npm's script launcher finds its own vendored host #476 keeps npm-installed Codex, the workflow's path, from being refused.claude-opus-5-5requires. A pin bump with checksums follows.