Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
The table of contents is too big for display.
Diff view
Diff view
  •  
  •  
  •  
11 changes: 5 additions & 6 deletions .github/workflows/eval-cache-check.yml
Original file line number Diff line number Diff line change
Expand Up @@ -21,12 +21,11 @@ jobs:

- run: pnpm install --frozen-lockfile

# Pinned to a known-good next.js commit. To adopt new/changed evals, bump this
# SHA in a PR that runs them for the experiments you're refreshing and
# `agent-eval keep`s the rest. The check below passes as long as every
# new/changed eval is either run or kept — so models may sit on an older eval
# version intentionally without going red.
- run: pnpm sync-evals 9e4d718de41bc2bceb687c73c2a60fdf6c5c4440
# Pinned to a known-good next.js canary commit. To adopt new/changed evals,
# bump this SHA in a PR that reruns them for the experiments you're
# refreshing and lists the remaining (experiment, eval) pairs in
# check-stale.mjs's ACCEPTED_STALE.
- run: pnpm sync-evals 0240fd39a5351a4a76c73a81058379a41e26c9ff

# The "which staleness is acceptable" policy lives in this repo, not the
# framework: check-stale.mjs reads `agent-eval status --json` and fails on
Expand Down
Loading
Loading