diff --git a/.changeset/svelte-bindings.md b/.changeset/svelte-bindings.md
deleted file mode 100644
index 456c5ac..0000000
--- a/.changeset/svelte-bindings.md
+++ /dev/null
@@ -1,11 +0,0 @@
----
-'@seamless-auth/svelte': minor
----
-
-First release of `@seamless-auth/svelte`, the Svelte binding for Seamless Auth (Svelte 5).
-
-- `createSeamlessAuth({ apiHost })` creates a session whose properties (`user`, `isAuthenticated`, `loading`, and the rest) are runes, with every auth action. `setSeamlessAuth` and `getSeamlessAuth` share it through context.
-- `@seamless-auth/svelte/kit` provides `requireAuth(auth, { roles })` and `requireGuest(auth)` `load` guards, and `createKitNavigator` for the bundled screens, for SvelteKit 2.26 and later, and SvelteKit 3. Each guard waits for the session to be read.
-- Sign-in screens (`SaLogin`, `SaVerifyOtp`, `SaMagicLinkSent`, `SaVerifyMagicLink`, `SaOAuthCallback`, `SaPasskeyLogin`, `SaRegisterPasskey`) to mount at your routes, themed with the same `--seamless-*` properties as the other bindings. They navigate through an `AuthNavigator`, so any router can drive them.
-
-The binding uses cookie transport only: tokens stay in the server adapter, and nothing is written where page scripts can read it.
diff --git a/packages/svelte/CHANGELOG.md b/packages/svelte/CHANGELOG.md
new file mode 100644
index 0000000..211a1c9
--- /dev/null
+++ b/packages/svelte/CHANGELOG.md
@@ -0,0 +1,12 @@
+# @seamless-auth/svelte
+
+## 0.1.0
+
+### Minor Changes
+
+- d1a70a1: First release of `@seamless-auth/svelte`, the Svelte binding for Seamless Auth (Svelte 5).
+  - `createSeamlessAuth({ apiHost })` creates a session whose properties (`user`, `isAuthenticated`, `loading`, and the rest) are runes, with every auth action. `setSeamlessAuth` and `getSeamlessAuth` share it through context.
+  - `@seamless-auth/svelte/kit` provides `requireAuth(auth, { roles })` and `requireGuest(auth)` `load` guards, and `createKitNavigator` for the bundled screens, for SvelteKit 2.26 and later, and SvelteKit 3. Each guard waits for the session to be read.
+  - Sign-in screens (`SaLogin`, `SaVerifyOtp`, `SaMagicLinkSent`, `SaVerifyMagicLink`, `SaOAuthCallback`, `SaPasskeyLogin`, `SaRegisterPasskey`) to mount at your routes, themed with the same `--seamless-*` properties as the other bindings. They navigate through an `AuthNavigator`, so any router can drive them.
+
+  The binding uses cookie transport only: tokens stay in the server adapter, and nothing is written where page scripts can read it.
diff --git a/packages/svelte/package.json b/packages/svelte/package.json
index 9226d16..88ba6f5 100644
--- a/packages/svelte/package.json
+++ b/packages/svelte/package.json
@@ -1,6 +1,6 @@
 {
   "name": "@seamless-auth/svelte",
-  "version": "0.0.0",
+  "version": "0.1.0",
   "description": "Svelte bindings for Seamless Auth: a rune-based session, SvelteKit guards, and optional sign-in screens.",
   "type": "module",
   "svelte": "./dist/index.js",