From fcd4a69c8deac0ef608b27633ecb01834ef653a2 Mon Sep 17 00:00:00 2001
From: "github-actions[bot]"
 <41898282+github-actions[bot]@users.noreply.github.com>
Date: Wed, 11 Nov 2026 13:44:20 +0000
Subject: [PATCH] chore: version packages

---
 .changeset/port-conflict-warnings.md      | 5 -----
 .changeset/unique-compose-project.md      | 5 -----
 .changeset/verify-contributor-guidance.md | 5 -----
 CHANGELOG.md                              | 8 ++++++++
 package.json                              | 2 +-
 5 files changed, 9 insertions(+), 16 deletions(-)
 delete mode 100644 .changeset/port-conflict-warnings.md
 delete mode 100644 .changeset/unique-compose-project.md
 delete mode 100644 .changeset/verify-contributor-guidance.md

diff --git a/.changeset/port-conflict-warnings.md b/.changeset/port-conflict-warnings.md
deleted file mode 100644
index 33e7f08..0000000
--- a/.changeset/port-conflict-warnings.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"seamless-cli": patch
----
-
-`seamless init` warns when another program already holds a port the local stack publishes (5173, 3000, 5312, 5432, and 5174 with a separate console), and `seamless check` fails on one. The stack publishes on 127.0.0.1 only, so a Vite dev server on `[::1]:5173` used to take `http://localhost:5173` in the browser while every check passed. Each warning says what the conflict breaks and how to find the program. `check` also asks the project's own compose file which services run, rather than matching container names across every running container.
diff --git a/.changeset/unique-compose-project.md b/.changeset/unique-compose-project.md
deleted file mode 100644
index 40b2f46..0000000
--- a/.changeset/unique-compose-project.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"seamless-cli": patch
----
-
-`seamless init` names each local stack's Compose project after its directory plus a random suffix, and no longer pins container names. A second project scaffolded under a name used before (such as the quickstart's `my-app`) used to share the first one's Compose project, so `docker compose up` ran the old project's built images, which crashed against the new starters (`does not provide an export named 'requirePermission'`), and reused its database. Two scaffolded projects can now also run side by side. Existing projects keep their compose file.
diff --git a/.changeset/verify-contributor-guidance.md b/.changeset/verify-contributor-guidance.md
deleted file mode 100644
index 4375e28..0000000
--- a/.changeset/verify-contributor-guidance.md
+++ /dev/null
@@ -1,5 +0,0 @@
----
-"seamless-cli": patch
----
-
-`seamless verify` run without a seamless-auth-api checkout now says it is a contributor tool, where to clone the API, and that `seamless check` is the command for a scaffolded project. From an npx or global install it no longer prints a path inside the npm cache, and `seamless verify --help` says the same up front.
diff --git a/CHANGELOG.md b/CHANGELOG.md
index ac7c57a..2c68773 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -1,5 +1,13 @@
 # seamless-cli
 
+## 0.30.1
+
+### Patch Changes
+
+- 3525c5d: `seamless init` warns when another program already holds a port the local stack publishes (5173, 3000, 5312, 5432, and 5174 with a separate console), and `seamless check` fails on one. The stack publishes on 127.0.0.1 only, so a Vite dev server on `[::1]:5173` used to take `http://localhost:5173` in the browser while every check passed. Each warning says what the conflict breaks and how to find the program. `check` also asks the project's own compose file which services run, rather than matching container names across every running container.
+- 3525c5d: `seamless init` names each local stack's Compose project after its directory plus a random suffix, and no longer pins container names. A second project scaffolded under a name used before (such as the quickstart's `my-app`) used to share the first one's Compose project, so `docker compose up` ran the old project's built images, which crashed against the new starters (`does not provide an export named 'requirePermission'`), and reused its database. Two scaffolded projects can now also run side by side. Existing projects keep their compose file.
+- 18619ea: `seamless verify` run without a seamless-auth-api checkout now says it is a contributor tool, where to clone the API, and that `seamless check` is the command for a scaffolded project. From an npx or global install it no longer prints a path inside the npm cache, and `seamless verify --help` says the same up front.
+
 ## 0.30.0
 
 ### Minor Changes
diff --git a/package.json b/package.json
index ec0d3c8..639c7b3 100644
--- a/package.json
+++ b/package.json
@@ -1,6 +1,6 @@
 {
   "name": "seamless-cli",
-  "version": "0.30.0",
+  "version": "0.30.1",
   "description": "The CLI for Seamless Auth, open source passwordless auth",
   "keywords": [
     "seamless-auth",