@xano/sdk 1.0.4 → 1.0.5

package/CHANGELOG.md

@@ -2,15 +2,27 @@
 
 All notable changes to [`@xano/sdk`](https://www.npmjs.com/package/@xano/sdk).
 
-This file is **generated** from the [GitHub releases](https://github.com/xanots/sdk/releases)
+This file is **generated** from the [GitHub releases](https://github.com/xano-sdk/sdk/releases)
 by `npm run changelog` — edit the release, not this file. Each entry summarizes
 one release and links to its full notes.
 
 ---
 
+## 1.0.4 — 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`
+
+---
+
 ## 1.0.3 — Agents and MCP servers pass preflight
 
-_2026-10-03_ · [release notes](https://github.com/xanots/sdk/releases/tag/v1.0.3)
+_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.
 
@@ -24,7 +36,7 @@ This patch release fixes `xanosdk preflight` on workspaces that have agents or M
 
 ## 1.0.2 — Fixtures can pin accepted hazards
 
-_2026-10-03_ · [release notes](https://github.com/xanots/sdk/releases/tag/v1.0.2)
+_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.
 
@@ -36,7 +48,7 @@ This patch release lets a def deliberately author three shapes the engine accept
 
 ## 1.0.1 — Safer local-engine records
 
-_2026-10-03_ · [release notes](https://github.com/xanots/sdk/releases/tag/v1.0.1)
+_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.
 
@@ -48,7 +60,7 @@ This patch release makes the local engine's record file safe under concurrent us
 
 ## 1.0.0 — Xano SDK, the new name
 
-_2026-10-02_ · [release notes](https://github.com/xanots/sdk/releases/tag/v1.0.0)
+_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.