From 8aa70242f3023f2dfd096a635e05016dfd4044ae Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Tue, 20 Oct 2026 19:01:59 +0000 Subject: [PATCH] chore: version packages --- .changeset/org-member-conflict-message.md | 5 ----- .changeset/owner-code.md | 7 ------- .changeset/pin-api-0-19-1.md | 7 ------- .changeset/seamless-service-token-env.md | 13 ------------ CHANGELOG.md | 25 +++++++++++++++++++++++ package.json | 2 +- 6 files changed, 26 insertions(+), 33 deletions(-) delete mode 100644 .changeset/org-member-conflict-message.md delete mode 100644 .changeset/owner-code.md delete mode 100644 .changeset/pin-api-0-19-1.md delete mode 100644 .changeset/seamless-service-token-env.md diff --git a/.changeset/org-member-conflict-message.md b/.changeset/org-member-conflict-message.md deleted file mode 100644 index 2bc2cba..0000000 --- a/.changeset/org-member-conflict-message.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"seamless-cli": patch ---- - -`seamless org members add` now says the user is already a member when the instance answers 409, instead of a bare `Request failed (409).` (an organization's creator is a member automatically, so adding yourself after `org create` hits this). A 404 on add no longer claims the organization is missing when it is the user. The other `org` and `users` commands name the action that failed and include the instance's own error message, for example `Could not update member (400: Organization must keep at least one owner).` diff --git a/.changeset/owner-code.md b/.changeset/owner-code.md deleted file mode 100644 index 6a3cf17..0000000 --- a/.changeset/owner-code.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"seamless-cli": minor ---- - -New `seamless owner-code` command prints a one-time code for the owner of a local stack, so the first admin finishes registering without reading container logs. Register in the browser with the owner address, and when the page asks for a code, run `npx seamless-cli owner-code` from the project directory. It waits for the auth server, reads `OWNER_EMAIL` from `auth/.env` or `docker-compose.yml` (or takes an address), and only talks to a local auth server. - -`seamless init` now ends with that step, and the generated AGENTS.md names it in its first admin section. diff --git a/.changeset/pin-api-0-19-1.md b/.changeset/pin-api-0-19-1.md deleted file mode 100644 index 6fc8ce6..0000000 --- a/.changeset/pin-api-0-19-1.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"seamless-cli": patch ---- - -New projects scaffold auth server v0.19.1, admin dashboard v0.10.0 and seamless-templates v0.20.0. The auth server includes the fixes for GHSA-9jg2-jjqq-3346 and GHSA-66gq-4pwg-33jq, and the starters are on the SDKs that work with its cross-device magic link confirmation. - -The generated auth server environment now holds the service token as `SEAMLESS_SERVICE_TOKEN`, the auth server's own name for it since 0.19.0, instead of `API_SERVICE_TOKEN`. The auth server's `.env.example` carries a placeholder under the new name, and the server refuses to start when the two names hold different values, so writing only the old name left `seamless init --auth=local` (which clones the auth server's main branch) unable to start. Re-running against an existing `auth/.env` reads either name. diff --git a/.changeset/seamless-service-token-env.md b/.changeset/seamless-service-token-env.md deleted file mode 100644 index cf8cd13..0000000 --- a/.changeset/seamless-service-token-env.md +++ /dev/null @@ -1,13 +0,0 @@ ---- -"seamless-cli": minor ---- - -Applications now read their service token as `SEAMLESS_SERVICE_TOKEN`, the name the managed portal already uses and the auth server's own name for it since 0.19.0. The generated auth server environment uses it too. - -- `seamless init`: the generated `docker-compose.yml` gives the `api` service (or a full-stack `web` service) `SEAMLESS_SERVICE_TOKEN`, with a comment saying it is the same secret as the `auth` service's. Connecting a managed application writes `SEAMLESS_SERVICE_TOKEN` into `api/.env`, and the values printed when there is no `api/` directory use the new name. -- `seamless add`: the backend's `.env` gets `SEAMLESS_SERVICE_TOKEN`, and the printed Node, Go, Rust and Python code reads it. -- `seamless verify`: the Express and Fastify reference apps read `SEAMLESS_SERVICE_TOKEN`, and the Next.js starter is given both names so starters from before the rename still run. - -Existing projects keep working. When a project's `.env` already has `API_SERVICE_TOKEN` and not `SEAMLESS_SERVICE_TOKEN`, `seamless add` and `seamless init` (connecting a managed application) update `API_SERVICE_TOKEN` in place, say so, and print code that reads that name, rather than adding a second variable the app does not read. - -The starters in `seamless-templates` that read `SEAMLESS_SERVICE_TOKEN` require this version. diff --git a/CHANGELOG.md b/CHANGELOG.md index 9d2f532..72d74f4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,30 @@ # seamless-cli +## 0.24.0 + +### Minor Changes + +- 9e63557: New `seamless owner-code` command prints a one-time code for the owner of a local stack, so the first admin finishes registering without reading container logs. Register in the browser with the owner address, and when the page asks for a code, run `npx seamless-cli owner-code` from the project directory. It waits for the auth server, reads `OWNER_EMAIL` from `auth/.env` or `docker-compose.yml` (or takes an address), and only talks to a local auth server. + + `seamless init` now ends with that step, and the generated AGENTS.md names it in its first admin section. + +- 59d583d: Applications now read their service token as `SEAMLESS_SERVICE_TOKEN`, the name the managed portal already uses and the auth server's own name for it since 0.19.0. The generated auth server environment uses it too. + + - `seamless init`: the generated `docker-compose.yml` gives the `api` service (or a full-stack `web` service) `SEAMLESS_SERVICE_TOKEN`, with a comment saying it is the same secret as the `auth` service's. Connecting a managed application writes `SEAMLESS_SERVICE_TOKEN` into `api/.env`, and the values printed when there is no `api/` directory use the new name. + - `seamless add`: the backend's `.env` gets `SEAMLESS_SERVICE_TOKEN`, and the printed Node, Go, Rust and Python code reads it. + - `seamless verify`: the Express and Fastify reference apps read `SEAMLESS_SERVICE_TOKEN`, and the Next.js starter is given both names so starters from before the rename still run. + + Existing projects keep working. When a project's `.env` already has `API_SERVICE_TOKEN` and not `SEAMLESS_SERVICE_TOKEN`, `seamless add` and `seamless init` (connecting a managed application) update `API_SERVICE_TOKEN` in place, say so, and print code that reads that name, rather than adding a second variable the app does not read. + + The starters in `seamless-templates` that read `SEAMLESS_SERVICE_TOKEN` require this version. + +### Patch Changes + +- e781293: `seamless org members add` now says the user is already a member when the instance answers 409, instead of a bare `Request failed (409).` (an organization's creator is a member automatically, so adding yourself after `org create` hits this). A 404 on add no longer claims the organization is missing when it is the user. The other `org` and `users` commands name the action that failed and include the instance's own error message, for example `Could not update member (400: Organization must keep at least one owner).` +- a672c49: New projects scaffold auth server v0.19.1, admin dashboard v0.10.0 and seamless-templates v0.20.0. The auth server includes the fixes for GHSA-9jg2-jjqq-3346 and GHSA-66gq-4pwg-33jq, and the starters are on the SDKs that work with its cross-device magic link confirmation. + + The generated auth server environment now holds the service token as `SEAMLESS_SERVICE_TOKEN`, the auth server's own name for it since 0.19.0, instead of `API_SERVICE_TOKEN`. The auth server's `.env.example` carries a placeholder under the new name, and the server refuses to start when the two names hold different values, so writing only the old name left `seamless init --auth=local` (which clones the auth server's main branch) unable to start. Re-running against an existing `auth/.env` reads either name. + ## 0.23.1 ### Patch Changes diff --git a/package.json b/package.json index bbd3aed..aade9e1 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "seamless-cli", - "version": "0.23.1", + "version": "0.24.0", "description": "The CLI for Seamless Auth, open source passwordless auth", "keywords": [ "seamless-auth",