Overview - Ai

ai

7 days30 days

Latest CI Pipeline Executions

Fuzzy

Succeeded
stricter-pnpm-deps-config
fe258bf0 fix(scripts): sanitize tilde prefix in OpenRouter alias model constant names (#574) The daily sync-models workflow has been failing for several weeks. Example: https://github.com/TanStack/ai/actions/runs/26025311706/job/76496996066 OpenRouter started returning model IDs prefixed with `~` to denote routing aliases (e.g. `~anthropic/claude-haiku-latest`, `~anthropic/claude-opus-latest`, ~16 in the current snapshot). These point to whatever the current canonical model is for that slot and are valid models users can call. The generator transformed the IDs into JavaScript identifiers verbatim, producing `const ~ANTHROPIC_CLAUDE_HAIKU_LATEST = {…}` — not a valid identifier. Prettier then bailed with `SyntaxError: Variable declaration expected. (4:7)` and the workflow failed. Fix: - Map a leading `~` in the model ID to `_` only when deriving the constant name. The original ID is still emitted as a string literal on the meta object's `id` field (`id: '~anthropic/claude-haiku-latest'`), so users can pass the exact ID to `chat({ model: '~anthropic/claude-haiku-latest' })` and the constant list (`OPENROUTER_CHAT_MODELS`) references the alias by that same ID. - Add a regex check inside `generateModelMetaString` that throws with a clear, actionable error if a generated constant name isn't a valid JS identifier. Future OpenRouter ID quirks will fail loudly at generation time instead of writing invalid TS that breaks later in the pipeline. Verified locally: `pnpm regenerate:models` now produces valid identifiers like `_ANTHROPIC_CLAUDE_HAIKU_LATEST` with the original `'~anthropic/...'` strings intact, and `pnpm exec prettier --write` on the generated file succeeds.
by Alem Tuzlak
Succeeded
stricter-pnpm-deps-config
fe258bf0 fix(scripts): sanitize tilde prefix in OpenRouter alias model constant names (#574) The daily sync-models workflow has been failing for several weeks. Example: https://github.com/TanStack/ai/actions/runs/26025311706/job/76496996066 OpenRouter started returning model IDs prefixed with `~` to denote routing aliases (e.g. `~anthropic/claude-haiku-latest`, `~anthropic/claude-opus-latest`, ~16 in the current snapshot). These point to whatever the current canonical model is for that slot and are valid models users can call. The generator transformed the IDs into JavaScript identifiers verbatim, producing `const ~ANTHROPIC_CLAUDE_HAIKU_LATEST = {…}` — not a valid identifier. Prettier then bailed with `SyntaxError: Variable declaration expected. (4:7)` and the workflow failed. Fix: - Map a leading `~` in the model ID to `_` only when deriving the constant name. The original ID is still emitted as a string literal on the meta object's `id` field (`id: '~anthropic/claude-haiku-latest'`), so users can pass the exact ID to `chat({ model: '~anthropic/claude-haiku-latest' })` and the constant list (`OPENROUTER_CHAT_MODELS`) references the alias by that same ID. - Add a regex check inside `generateModelMetaString` that throws with a clear, actionable error if a generated constant name isn't a valid JS identifier. Future OpenRouter ID quirks will fail loudly at generation time instead of writing invalid TS that breaks later in the pipeline. Verified locally: `pnpm regenerate:models` now produces valid identifiers like `_ANTHROPIC_CLAUDE_HAIKU_LATEST` with the original `'~anthropic/...'` strings intact, and `pnpm exec prettier --write` on the generated file succeeds.
by Alem Tuzlak
Succeeded
stricter-pnpm-deps-config
4bdbc79e security: stricter pnpm config blockExoticSubdeps & trustPolicy
by Sheraff
Succeeded
stricter-pnpm-deps-config
4bdbc79e Merge 713edfdb5ba922f14cc7363d14bf75f4784cc9d6 into 6a23e80efe0c8d641e0a29e9a30b2735163f55b0
by Flo