feat(connectors): upgrade Fire Pass router to Kimi K2.6 Turbo
Fireworks rolled out the kimi-k2p6-turbo router as the new Fire Pass target; the k2p5-turbo route will start refusing Fire-Pass-only callers. Bump the router id and display name in connector-catalog, apikey connector definition, model-resolver, and capability-seed so the desktop catalog, the renderer's onboarding rail, the capability matrix, and the runtime model resolver all point at the same model.
This commit is contained in:
1 parent
0e1710065f
commit
07d9c00fab
4 files changed
+9
-9
No files matched your search
@@ -236,9 +236,9 @@ const API_KEY_ENTRIES: ConnectorCatalogEntry[] = [
|
||||
provider: "fireworks-firepass",
|
||||
label: "Fireworks Fire Pass",
|
||||
description: "Fireworks Fire Pass — subscription bundle. Same FIREWORKS_API_KEY.",
|
||||
defaultModel: "accounts/fireworks/routers/kimi-k2p5-turbo",
|
||||
defaultModel: "accounts/fireworks/routers/kimi-k2p6-turbo",
|
||||
auth: { type: "api_key", envKey: "FIREWORKS_API_KEY" },
|
||||
notes: "Fire Pass uses the dedicated router id accounts/fireworks/routers/kimi-k2p5-turbo documented at docs.fireworks.ai/firepass.",
|
||||
notes: "Fire Pass uses the dedicated router id accounts/fireworks/routers/kimi-k2p6-turbo documented at docs.fireworks.ai/firepass.",
|
||||
},
|
||||
];
|
||||
|
||||
|
||||
Reference in new issue
Block a user