v1.0.5 — The Xano Engine is the default

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.

npm install @xano/sdk@1.0.5

⚠️ xanosdk deploy goes to the Xano Engine by default

With neither --ephemeral nor --to, deploy now runs your code on the Xano Engine on this machine. It needs no account and keeps rows across redeploys with --keep-data. Add --ephemeral to get the old behavior, a disposable ephemeral on Xano's cloud. --to workspace and --to tenant:<name> are unchanged. --ephemeral together with --local or --to is refused as two destinations, and --name / --expires-hours on a bare deploy now tell you to add --ephemeral. Every rerun hint that creates or refreshes an ephemeral now includes --ephemeral.

xanosdk deploy ./xano/index.ts              # Xano Engine (default)
xanosdk deploy ./xano/index.ts --ephemeral  # ephemeral on Xano's cloud (the old default)

CI: a pipeline that runs a bare xanosdk deploy to get a preview URL must add --ephemeral.

⚠️ The engine is local in the CLI

The old spellings are refused, not aliased.

Before (1.0.4)	Now
deploy --local-engine[=<v|url|path>]	deploy --local[=<v|url|path>]
--to local-engine, local-engine:<name>	--to local, local:<name>
xanosdk local-engine list|token|stop|update|cache	xanosdk local list|token|stop|update|cache
--local (project-local ./.xano/auth.json)	--local-auth
XANOSDK_LOCAL_ENGINE_HOME, _OVERRIDE, _TOKEN	XANOSDK_ENGINE_HOME, _OVERRIDE, _TOKEN
package.json pin "localEngine": "vX.Y.Z"	"engine": "vX.Y.Z"
--json: "kind": "local-engine", localEngine key	"kind": "local", engine key
Warning codes local-engine.*	local.* (e.g. local.import-failed)

--local used to select the project-local credential file, so that flag is now --local-auth. An old localEngine pin is no longer read: the next deploy runs the latest engine and pins it under engine, so rename the key if you want to stay on your version. The engine cache stays at ~/.xanosdk/local-engine, so no engine needs downloading again.

xanosdk publish reaches the Xano Engine

xanosdk publish <dir> --to local (or local:<name>) uploads a built frontend to the engine's own static host, including a SvelteKit server half, without re-importing the backend. A bare publish after a local deploy goes there too. It uses the engine's own token, so no Xano credential is read and nothing prompts. --release and --branch are refused there. An engine too old to host static sites gets a message naming xanosdk local update.

⚠️ Scaffolded projects deploy locally first

In a project xanosdk init writes:

• npm run xano:deploy deploys the backend to the Xano Engine with --keep-data.
• npm run xano:deploy:ephemeral builds the frontend and ships both to an ephemeral (the old xano:deploy).
• xano:deploy:local-engine is removed.

The next steps init prints, the scaffolded README, AGENTS.md and .env.example follow the same order. Existing projects keep the scripts they have. Rename them by hand if you want the new layout.

The README and scaffolded README introduce Xano

The repository README now opens with Xano, the platform, and puts the Xano Engine first in the Quickstart, followed by ephemerals and then workspaces. Reference material moved into guides/, including a new Reading a compiled bundle guide. A scaffolded or pulled project's README now opens with a "Built on Xano" header and closes with links to the SDK guides and Xano's docs.

The SDK lives at github.com/xano-sdk/sdk

Package metadata, docs and scaffolded links now point at xano-sdk/sdk. It receives the source and notes for each release, and takes issues and security advisories.

Full changelog: v1.0.4...v1.0.5