Release Post for v2.0-stable (#1812) * Release Post for v2.0-stable * fix(release): resolve v2.0-stable docs build blockers * chore(release): update v2.0-stable post title * Update website/releases/v2.0-stable.md * fix cdc tag * cdc tag fix * fix(releases): migrate change data capture tag to cdc * docs(release): version v2.0-stable as latest Snapshot docs/ into versioned_docs/version-2.0.x/ via create-release.sh, promoting v2.0 to latest (/docs) and keeping trunk as Next (/docs/next). Fix off-by-one ../ in non-markdown links across 36 index files (in both version-2.0.x and trunk docs/) that resolve at /docs/next but escape above the docs root when built as the latest version, plus a cross-version anchor leak in v1.7 (scalar_functions#embed). Markdown (.md) links untouched. Verified with a clean npm run build. --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>

docs(datasets): a time_format mismatch fails the dataset, and iso8601 on a timestamp or date column is ignored with a warning (#2325) * docs(datasets): a time_format mismatch fails the dataset, and iso8601 on a timestamp or date column is ignored with a warning (spiceai/spiceai#14777) * docs(datasets): a string time_column needs time_format iso8601 (spiceai/spiceai#14777)

docs(spicepod embeddings): complete the embeddings 'from' prefix list The Embeddings YAML reference listed three accepted 'from' prefixes (huggingface, file, openai). EmbeddingPrefix::try_from accepts eight: openai, azure, google, huggingface, file, databricks, bedrock, and model2vec. Each omitted prefix has its own provider page under components/embeddings/, so the reference page was the only surface claiming they are unsupported. Version-scoped from the enum at each release's latest tag: v1.5.2 6 prefixes (no google, no model2vec) v1.6.1 - v1.10.4 7 prefixes (no google) v1.11.6, v2.0.1, v2.1.1 8 prefixes

Release Post for v2.0-stable (#1812) * Release Post for v2.0-stable * fix(release): resolve v2.0-stable docs build blockers * chore(release): update v2.0-stable post title * Update website/releases/v2.0-stable.md * fix cdc tag * cdc tag fix * fix(releases): migrate change data capture tag to cdc * docs(release): version v2.0-stable as latest Snapshot docs/ into versioned_docs/version-2.0.x/ via create-release.sh, promoting v2.0 to latest (/docs) and keeping trunk as Next (/docs/next). Fix off-by-one ../ in non-markdown links across 36 index files (in both version-2.0.x and trunk docs/) that resolve at /docs/next but escape above the docs root when built as the latest version, plus a cross-version anchor leak in v1.7 (scalar_functions#embed). Markdown (.md) links untouched. Verified with a clean npm run build. --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>

Release Post for v2.0-stable (#1812) * Release Post for v2.0-stable * fix(release): resolve v2.0-stable docs build blockers * chore(release): update v2.0-stable post title * Update website/releases/v2.0-stable.md * fix cdc tag * cdc tag fix * fix(releases): migrate change data capture tag to cdc * docs(release): version v2.0-stable as latest Snapshot docs/ into versioned_docs/version-2.0.x/ via create-release.sh, promoting v2.0 to latest (/docs) and keeping trunk as Next (/docs/next). Fix off-by-one ../ in non-markdown links across 36 index files (in both version-2.0.x and trunk docs/) that resolve at /docs/next but escape above the docs root when built as the latest version, plus a cross-version anchor leak in v1.7 (scalar_functions#embed). Markdown (.md) links untouched. Verified with a clean npm run build. --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>

docs(snapshots): snapshots.location must be a URI; a bare filesystem path is rejected

Release Post for v2.0-stable (#1812) * Release Post for v2.0-stable * fix(release): resolve v2.0-stable docs build blockers * chore(release): update v2.0-stable post title * Update website/releases/v2.0-stable.md * fix cdc tag * cdc tag fix * fix(releases): migrate change data capture tag to cdc * docs(release): version v2.0-stable as latest Snapshot docs/ into versioned_docs/version-2.0.x/ via create-release.sh, promoting v2.0 to latest (/docs) and keeping trunk as Next (/docs/next). Fix off-by-one ../ in non-markdown links across 36 index files (in both version-2.0.x and trunk docs/) that resolve at /docs/next but escape above the docs root when built as the latest version, plus a cross-version anchor leak in v1.7 (scalar_functions#embed). Markdown (.md) links untouched. Verified with a clean npm run build. --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>

docs(models): paged attention is requested automatically, not unconditionally enabled The local-model paged-attention note collapsed three branches into one absolute sentence. `MistralLlama::paged_attention_config` returns `None` when the device is CPU or when the build is not `all(feature = "cuda", target_family = "unix")`, and the engine downgrades to dense attention again for architectures with no paged kernel (the Multi-head Latent Attention GGUFs) — so a CUDA+Unix build is necessary, not sufficient. From v2.2.0 (spiceai/spiceai#11990) the note is also wrong to say no configuration is needed: `FileModelParams::paged_attention` accepts `auto` (default) or `disabled`, and `disabled` forces dense attention. It is a `from: file:` parameter only — `HuggingFaceModelParams` has no such field and `from_hf` calls `paged_attention_config` unconditionally. Scoped accordingly: the branch distinction lands in v2.0.x-v2.3.x and vNext; the escape hatch only in v2.2.x, v2.3.x and vNext.

docs(runtime): runtime.auth.api-key.keys is required

docs(spicepod tools): fix broken MCP example (mcp_endpoint is not a parameter) The Tools spicepod reference example configured an MCP tool as 'from: mcp' with 'params.mcp_endpoint: http://localhost:3000/sse'. None of that loads: - 'mcp_endpoint' is not a parameter. It has never appeared in spiceai/spiceai; the MCP tool factory only reads 'mcp_args', 'mcp_auth_token', and 'mcp_headers'. - The MCP server address comes from the 'from' field, parsed as 'mcp:<target>' via split_once(':'), so a bare 'from: mcp' is rejected at load with 'Invalid component from field. Expected: mcp:<tool_id>'. - '/sse' reflects the SSE transport removed in favour of Streamable HTTP; MCPType has only StreamableHttp and Stdio variants. Replace the example with a valid Streamable HTTP tool, and document the 'mcp:<target>' forms under 'from' and the real MCP params under 'params'.

docs(cayenne): file-mode Cayenne rejects refresh_append_overlap Surfaced by spiceai/spiceai#13680, which had to comment the setting out of the repo-root sample spicepod because Cayenne refuses to load a dataset that sets it.

Release Post for v2.0-stable (#1812) * Release Post for v2.0-stable * fix(release): resolve v2.0-stable docs build blockers * chore(release): update v2.0-stable post title * Update website/releases/v2.0-stable.md * fix cdc tag * cdc tag fix * fix(releases): migrate change data capture tag to cdc * docs(release): version v2.0-stable as latest Snapshot docs/ into versioned_docs/version-2.0.x/ via create-release.sh, promoting v2.0 to latest (/docs) and keeping trunk as Next (/docs/next). Fix off-by-one ../ in non-markdown links across 36 index files (in both version-2.0.x and trunk docs/) that resolve at /docs/next but escape above the docs root when built as the latest version, plus a cross-version anchor leak in v1.7 (scalar_functions#embed). Markdown (.md) links untouched. Verified with a clean npm run build. --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>