feat: check the model catalog against the latest release before publishing (#11007)

pi.dev serves each published catalog to released pi >= MINIMUM_PI_VERSION.
Compile the latest release's pi-ai against its built-in models overlaid by
the new catalog, so a catalog it cannot handle (e.g. kimi-coding moving to
openai-completions) fails in CI instead of breaking released clients.
MINIMUM_PI_VERSION moves to scripts/model-catalog-minimum-version.mjs.
This commit is contained in:
David Brailovsky 2026-10-15 21:21:57 +02:00 • committed by GitHub
parent ae7b16d43b
commit 4954d76050
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
5 changed files with 162 additions and 5 deletions

View file

@ -34,6 +34,7 @@
"update:model-catalog-pin": "node scripts/update-model-catalog-pin.mjs",
"eval": "npm run eval --workspace=@earendil-works/pi-evals --",
"check:model-catalog": "node scripts/publish-model-catalog.mjs --input .artifacts/model-catalog --dry-run",
"check:model-catalog-compat": "node scripts/check-model-catalog-compat.mjs",
"profile:tui": "node scripts/profile-coding-agent-node.mjs --mode tui",
"profile:rpc": "node scripts/profile-coding-agent-node.mjs --mode rpc",
"test": "npm run test:scripts && npm run test --workspaces --if-present",