[scott]

[2.8.1] - 2026-10-22

Documentation

• The docs site adds an Inference providers page. It lists each shipped provider's prefix, key environment variable, base URL override, how /model lists models, and what deploy forwards. OpenRouter stays the default. Direct providers are xAI, OpenAI (openai-api/), Google Gemini, Anthropic (anthropic-api/), DigitalOcean serverless inference, and local Ollama. openai/, anthropic/, google/, and x-ai/ stay on OpenRouter. bedrock/ is reserved and is not shipped. (#424)
• A cast provider / /provider page covers listing providers, enabling one, --token -, --url, keychain storage, and the token file at ~/.cast/tokens/inference/<key>.token. The active provider is the prefix on defaults.builder_model. (#424)
• The builder-model page lists direct provider prefixes next to the OpenRouter ids: openai-api/, xai/, gemini/, anthropic-api/, digitalocean/, and ollama/. (#424)
• The Known models reference is rewritten from python/cast/providers/manifest.json and getModels(). It no longer uses KNOWN_MODELS. (#424)
• Each model in the docs manifest records a provider field (the vendor segment of the id) and an inferenceProvider field (the manifest row key). (#424)

Changesets

Main has no pending changeset files. #424 did not add one (.changeset/ still holds only README.md and config.json). Nothing was deleted. The 2.8.1 notes are written by hand, the same way #422 wrote the 2.8.0 notes after consuming its changesets.

cast-cli and cast-tui changelogs record that docs commit as a patch change, matching the shared version bump.

Docs changelog page

extract-changelog.ts and the changelog page now keep a Documentation section. Without that, the 2.8.1 bullets would stay in the raw markdown and would not render.

Release workflow after merge

.github/workflows/release.yml finds no changesets on this commit, so changesets/action@v1 does not open a Version Packages pull request. It runs npx changeset tag, which creates cast-cli@2.8.1 and cast-tui@2.8.1. The private root package is not tagged.

The action's createGithubReleases input defaults to true, so it also opens GitHub releases for those two package tags. That is the same pair v2.8.0 already published. It does not create v2.8.1.

published is then true. The next step reads the root package.json version (2.8.1) and runs gh release create v2.8.1. That tag does not exist, so this creates it. It does not recreate v2.8.0.

Nothing in that path fails the previous "GitHub Actions is not permitted to create or approve pull requests" check, and nothing creates a second v2.8.1 tag or release. Generated notes start at the second-newest v* tag (v2.7.0), so they include commits already shipped in v2.8.0. That is the same notes range the workflow used for earlier releases.

This pull request does not create tags, GitHub releases, or npm publishes. Merging it is what starts that workflow.

  

[github-actions]

Test Coverage Report

Component	Coverage
No coverage reports available.

Provider smoke: pass (26 passed, 0 failed, 2 skipped)
CLI snapshots: pass (13 passed, 0 failed)
PR vs main: no new failures (0 already failing on main)