build: upgrade to Node.js 26 LTS and latest packages (React 19, TypeScript 7, Tailwind CSS 4) (#2451) * ci: run workflows on Node.js 26 and update actions Node.js 26 entered Active LTS on 2026-10-28 and Node.js 24 moved to maintenance on 2026-10-20. - actions/checkout v3/v4 -> v7 - actions/setup-node v4 -> v7, node-version 24 -> 26 - actions/github-script v7 -> v9 - actions/labeler v5 -> v7 - cloudflare/wrangler-action v3.14.1 -> v4.1.3 - spiceai/pulls-with-spice-action v1.0.7 -> v2.0.0 (v3.0.0 is a prerelease) * fix(website): make the typecheck pass under TypeScript 7 npm run typecheck previously ran out of memory because tsconfig.json included build/ and .docusaurus/. Exclude them, as upstream Docusaurus does. TypeScript 7 removes baseUrl, which @docusaurus/tsconfig 3.10 still sets. Unset it and redeclare the @site/* path relative to this tsconfig. Fix the errors the typecheck then reports: - Resolve two bare imports that only worked through baseUrl. - Import ProcessedFile from the module that exports it. - Type the Quote props (TypeScript 7 enables strict by default). - Add the Font Awesome Slack icon that the Slack link in Social expects; it still referenced a Discord icon that never existed. * build(deps): upgrade all packages, including React 19, TypeScript 7 and Tailwind CSS 4 Require Node.js 26 (Active LTS) and move every direct dependency to its latest release. The lockfile is regenerated, so transitive dependencies are current too. Majors: react/react-dom 18 -> 19, typescript 5.9 -> 7.0, tailwindcss 3 -> 4. tailwindcss-animate is replaced by tw-animate-css, and postcss-import is removed because @tailwindcss/postcss resolves imports itself. Tailwind CSS 4 migration, keeping rendered output identical: - Move tailwind.config.ts into CSS (@theme inline). Pin the v3 values that v4 changed: neutral and red-700 colors, px breakpoints, and rem line heights for text-xs/sm/base/xl/2xl. - Scope utilities under .tailwind by nesting @tailwind utilities, which replaces v3's important: '.tailwind' and keeps them unlayered so they still win over Infima. - Generate utilities only from src/ (the v3 content glob) and exclude container, which v3 disabled in favor of Infima's .container. - Keep hover styles on touch devices, as in v3. - Replace theme() calls in preflight.css with the values v3 resolved. - Rename utilities whose meaning changed: outline-none -> outline-hidden, backdrop-blur-sm -> backdrop-blur-xs, bg-gradient-to-* -> bg-linear-to-*. - leading-* now overrides responsive text-* line heights: drop the redundant leading-8 from Title and add md:leading-8 to Paragraph. - Dialog: drop the slide offsets that compensated for v3 transforms, and use gap instead of space-*, matching shadcn's Tailwind 4 version. * ci: pin third-party actions to commit SHAs Resolves CodeQL actions/unpinned-tag alerts #13 and #14: a mutable tag can be repointed, and the Deploy step passes the Cloudflare API token to wrangler-action. The version stays in a trailing comment. - cloudflare/wrangler-action v4.1.3 -> 953926a2e2182532811c01a25e53647d93bf07c0 - spiceai/pulls-with-spice-action v2.0.0 -> 61ef22e4a17be07209f0811fbfe4f0deb2e490a4

docs(accelerators): document cayenne_scan_concurrency, cayenne_pk_keyset_cache_mb, cayenne_bake_deletion_index_trigger, cayenne_cdc_mem_tier_shards, and arrow_sort_columns (#2481) * docs(accelerators): document cayenne_scan_concurrency, cayenne_pk_keyset_cache_mb, cayenne_bake_deletion_index_trigger, cayenne_cdc_mem_tier_shards, and arrow_sort_columns * docs(accelerators): drop the first-version keyset fallback and state the key-based prerequisite for cayenne_cdc_mem_tier_shards --------- Co-authored-by: Emma Spice <emma@EmmasMacStudio.localdomain>

Add `website/public/openapi.json` (#809) * add website/public/openapi.json * Update .gitignore --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>

Add blog (#735) * Add blog * Update * Update authors.yml * Update v1.0-rc.4.md * Fixes * Update v0.20-beta.md * Update v0.19.4-beta.md * Update v0.17.2-beta.md * Update v0.17.1-beta.md * Update v0.17-beta.md * Update v0.13.3-alpha.md * Update v0.12.1-alpha.md * Update v0.10-alpha.md * Update v0.7-alpha.md * Update v0.6-alpha.md * Update v0.5.1-alpha.md * Update v0.5-alpha.md * Update v0.4-alpha.md * Update v0.3-alpha.md * Update authors, update releases (#736) * Update authors.yml * Update v0.19-beta.md * Update v1.0-rc.2.md * Add website * add jeadie author, add to releases * Fixes * Update packages * Fixes for react * Fixes * Merge * Update names * Use hosted generator * Tweak * fix scoped tailwind styles * Fix images * use scpoed preflight.css, adjust home page styles * Update links * Update inline HTML to Markdown * add evgenii to authors * fix expressions * fix static links * fix linnks * fix url docs links * fix blog links * prefix docs links with /docs * fix fonts and tweak styles * apply fonts * add sgrebnov to authors * Fix broken links --------- Co-authored-by: Phillip LeBlanc <phillip@spiceai.io> Co-authored-by: peasee <98815791+peasee@users.noreply.github.com> Co-authored-by: jeadie <jack@spice.ai> Co-authored-by: Evgenii Khramkov <evgenii@spice.ai> Co-authored-by: Sergei Grebnov <sergei.grebnov@gmail.com>

Use custom font in OG image (#808) * Use custom font in OG image * fix * fix * fix prettier * try using jsx * fix * adjust dimensions * fix * adjust size * tweak * test blog cover * fix * fix * fix * fix * use prod url * fix title size * Update v1.0-stable.md --------- Co-authored-by: Luke Kim <80174+lukekim@users.noreply.github.com>

chore: make AGENTS.md the canonical agent instructions (#2239) * chore: make AGENTS.md the canonical agent instructions * chore: remove CLAUDE.md; AGENTS.md is canonical

fix(codeowners): point the owner rule at the team that actually exists `CODEOWNERS` named `@spiceai/maintainers`, which GitHub cannot resolve, so the catch-all rule matched every file and applied to nobody. The practical effect was that no PR in this repo was ever auto-assigned a reviewer: `reviewDecision` sat at REVIEW_REQUIRED while `reviewRequests` stayed empty. The org's maintainer team is `@spiceai/spice-core-maintainers` — the same slug `spiceai/spiceai` uses, where the codeowners errors endpoint returns clean. It holds the `maintain` role here, so it satisfies the write-access requirement for a valid owner. Fixes #2097

Add copilot instructions (#613)

v0.7-alpha updates (#100) * Spicepod v0.2 specification. * Remove training * Remove actions * Fixed name of spicepod * Add version + kind * Add kind+version to samples * Updates for medata, datasets, functions, and models concepts * Add dependsOn * Add dependencies * Update dataset spicepod reference (#102) * Update dataset spicepod reference * Update datasets.md * Update LICENSE * Update getting started and core concepts (#103) * Update Core Concepts * Cleanup installation instructions * cleanup old references * update acknowledgments * fix title * update cli * cleanup getting started * Update spiceaidocs/config.toml Co-authored-by: Phillip LeBlanc <phillip@spiceai.io> * use local images * fix images * final changes --------- Co-authored-by: Phillip LeBlanc <phillip@spiceai.io> --------- Co-authored-by: Phillip LeBlanc <phillip@leblanc.tech> Co-authored-by: Phillip LeBlanc <phillip@spiceai.io> Co-authored-by: Evgenii Khramkov <evgenii@spice.ai>

docs(readme): describe the Cloudflare Pages deployment and why Cloudflare Git builds are off (#2407) * docs(readme): describe the Cloudflare Pages deployment and why Cloudflare Git builds are off The README said the site is hosted on GitHub Pages. It is hosted on Cloudflare Pages: the build_and_publish workflow builds website/ and uploads it with wrangler pages deploy. Add a Deployment section that covers production and preview deploys, why pull requests from forks are not deployed, and why Cloudflare's own Git builds are turned off. Connecting the repository to the Pages project on 2026-10-18 turned those builds on, and they failed on every push because the project's root directory is empty. Also correct the Node.js prerequisite: website/package.json has required Node 24 or later since #986. * docs(readme): list every workflow change needed to build in Cloudflare instead Removing only the deploy step would leave the pull request comment step posting an empty deployment URL, and the Algolia reindex running before Cloudflare publishes the new site. Addresses Copilot's review on #2407. * docs(readme): turn Cloudflare Git deployments back on when moving builds to Cloudflare The migration steps changed the project settings and removed the Actions deploy step, but never re-enabled automatic Git deployments, which would leave no deploy path. Addresses Copilot's second review on #2407.