smashimo/oh-my-pi
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

test(catalog): pinned copilot grok-4.5 migration to the responses route

Browse Source 
- The regenerated bundle (merged with PR #8021) now ships a
  responses-route github-copilot/grok-4.5, so the id legitimately
  resurfaces from the bundle when the migration refresh fails; the
  contract worth defending is that the stale cached completions route
  never returns and the unbundled long-context variant stays dropped.
This commit is contained in:
can1357
2026-08-08 20:57:10 +02:00
parent bf04fbfc8d
commit 60d4cb997e
1 changed files with 6 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
packages/catalog/test/github-copilot-model-limits.test.ts
+6 -1
View File
@@ -421,7 +421,12 @@ describe("github copilot model limits mapping", () => {
const { models } = await manager.refresh("online-if-uncached");
expect(fetchMock).toHaveBeenCalledTimes(1);
expect(models.find(candidate => candidate.id === "grok-4.5")).toBeUndefined();
// The bundled catalog now ships a responses-route grok-4.5, so the id
// resurfaces from the bundle after the failed refresh. The migration
// contract is that the stale cached COMPLETIONS route never comes
// back — and the cached long-context variant has no bundled entry,
// so it stays dropped.
expect(models.find(candidate => candidate.id === "grok-4.5")?.api).toBe("openai-responses");
expect(models.find(candidate => candidate.id === "grok-4.5-1m")).toBeUndefined();
} finally {
await fs.rm(tempDir, { recursive: true, force: true });