> ## Documentation Index
> Fetch the complete documentation index at: https://sdk.docs.xano.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Changelog

> Every @xano/sdk release, newest first, with a summary and a link to its full release notes.

<Update label="1.0.9">
  See the [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.9).
</Update>

<Update label="1.0.8" description="Deploys stop overwriting Xano edits">
  *2026-10-13* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.8)

  A deploy to your workspace no longer overwrites edits a teammate made in Xano. This release also fixes a false `preflight` failure on zero-argument filters and warns when an agent run leaves its tools off.

  * `deploy --to workspace` refuses to overwrite edits made in Xano
  * `preflight` no longer fails on zero-argument filters
  * A warning when an agent run leaves its tools off
</Update>

<Update label="1.0.7" description="Your coding agent gets a backend">
  *2026-10-07* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.7)

  This release is about coding agents working on a Xano backend. An agent in a Xano project now reaches the Xano Engine on your machine over MCP: it can read tables and rows, seed data, and run functions and tests with nothing to configure by hand. `xanosdk init` adds a backend to an app you already have instead of refusing it, and the new `xano-backend` agent skill points agents there. The `AGENTS.md` that `init` writes now briefs an agent on a project with a backend. It also fixes `.ts` entries failing on Node 20 and 22 with tsx 4.23.

  * Coding agents reach the Xano Engine over MCP
  * `init` adds a backend to an app you already have
  * The `xano-backend` agent skill
  * `AGENTS.md` is a backend brief, not a command list
  * The brief's authoring example is compile-checked
  * `.ts` entries load again with tsx 4.23 on Node 20 and 22
</Update>

<Update label="1.0.6" description="Request types reach the frontend">
  *2026-10-05* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.6)

  This release types every request a frontend sends from `routes.gen.ts` alone, opens that file to marketplace modules so runtime validators can sit beside the types, and teaches `workspace diff` to say which side changed since the project and a workspace branch last matched. ⚠️ One behavior break: `s.db.transaction` no longer accepts `as`, which always bound `null`.

  * `routes.gen.ts` types every request the frontend sends
  * Toolchain modules add their own section to `routes.gen.ts`
  * `workspace diff` says which side changed since the last sync
  * ⚠️ `s.db.transaction` no longer takes `as`
  * A required input that carries a default is flagged
  * The scaffolded README keeps its platform section
</Update>

<Update label="1.0.5" description="The Xano Engine is the default">
  *2026-10-05* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.5)

  This release makes the **Xano Engine**, the engine that runs on your machine, the default place your code goes. A bare `xanosdk deploy` now runs your backend locally with no Xano account, and `--ephemeral` sends it to Xano's cloud as the bare command used to. The engine is now called `local` everywhere in the CLI, and `publish` can put a frontend on it. ⚠️ Scripts that run a bare `deploy` expecting an ephemeral, or that use the `local-engine` spellings, need the changes below.

  * ⚠️ `xanosdk deploy` goes to the Xano Engine by default
  * ⚠️ The engine is `local` in the CLI
  * `xanosdk publish` reaches the Xano Engine
  * ⚠️ Scaffolded projects deploy locally first
  * The README and scaffolded README introduce Xano
  * The SDK lives at github.com/xano-sdk/sdk
</Update>

<Update label="1.0.4" description="Marketplace moves to its new catalogue">
  *2026-10-03* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.4)

  This patch release moves `xanosdk marketplace` to the catalogue's new home. The CLI now reads modules from a new default host, `XANOSDK_MARKETPLACE_URL` works with a tenant or ephemeral base, and a module withdrawn from the marketplace is refused by `install` again. No call-site changes are needed.

  * The marketplace reads from its new catalogue host
  * `XANOSDK_MARKETPLACE_URL` keeps the path on its base
  * A module withdrawn from the marketplace is refused by `install`
</Update>

<Update label="1.0.3" description="Agents and MCP servers pass preflight">
  *2026-10-03* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.3)

  This patch release fixes `xanosdk preflight` on workspaces that have agents or MCP servers, and makes pulling an existing workspace into code more reliable. Agents and MCP servers without sign-in no longer fail the round trip. Workspaces pulled with `export`/codegen now re-export as they were stored and the generated tree typechecks, including shapes older workspaces carry.

  * `preflight` no longer fails every agent and MCP server without `oauth`
  * UUID primary keys keep their stored default
  * Pulled workspaces decode more statements to typed code
  * Guards the engine accepts are now warnings a def can allow
  * Workspace defects are reported and the tree still compiles
</Update>

<Update label="1.0.2" description="Fixtures can pin accepted hazards">
  *2026-10-03* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.2)

  This patch release lets a def deliberately author three shapes the engine accepts but 1.0 refused outright: an active cache with `ttl: 0`, a call passing an input its target does not declare, and a lambda body that does not parse. Each is still flagged by default, and `export --strict` still fails on it, but a fixture that pins the engine's behavior for that input can now say so.

  * `cache.ttl` of 0 is a warning a def can accept
  * Passing an input the target does not declare is a warning a def can accept
  * `lam.raw(code, { unchecked: true })` sends a body that does not parse
</Update>

<Update label="1.0.1" description="Safer local-engine records">
  *2026-10-03* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.1)

  This patch release makes the local engine's record file safe under concurrent use and removes the SDK's handling of its retired package names. If you run several local-engine deploys or stops at once, they no longer undo each other's bookkeeping.

  * Concurrent local-engine deploys and stops no longer lose each other's records
  * `local-engine stop --all` keeps the record of an engine a concurrent deploy just started
  * The SDK no longer handles its retired package names
</Update>

<Update label="1.0.0" description="Xano SDK, the new name">
  *2026-10-02* · [release notes](https://github.com/xano-sdk/sdk/releases/tag/v1.0.0)

  The SDK is now **Xano SDK**, published as `@xano/sdk` and restarting at 1.0.0. The CLI is `xanosdk`, and add-on modules ship as `@xano-sdk/*`. The earlier `@xanots/sdk` 0.0.x and `@xanots/core` 2.0.x lines are retired.

  * The package is now @xano/sdk
  * Modules publish as @xano-sdk/\*
  * ⚠️ The CLI is xanosdk
  * ⚠️ XANOSDK\_\* env vars and the xanosdk project block
  * Docs and messages say Xano SDK
</Update>

***

*Generated from @xano/sdk 1.0.9.*


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.