From c85fd0379867ddadf47e210d03b2c6ef6bdef50c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sun, 13 Sep 2026 15:52:16 +0000 Subject: [PATCH] chore: version packages --- .changeset/mobile-template-kind.md | 21 ------------ .changeset/verify-pack-client-workspace.md | 16 ---------- CHANGELOG.md | 37 ++++++++++++++++++++++ package.json | 2 +- 4 files changed, 38 insertions(+), 38 deletions(-) delete mode 100644 .changeset/mobile-template-kind.md delete mode 100644 .changeset/verify-pack-client-workspace.md diff --git a/.changeset/mobile-template-kind.md b/.changeset/mobile-template-kind.md deleted file mode 100644 index 51fec90..0000000 --- a/.changeset/mobile-template-kind.md +++ /dev/null @@ -1,21 +0,0 @@ ---- -'seamless-cli': minor ---- - -`seamless init` learns the `mobile` template kind. - -`seamless-templates` gains a third kind next to `web` and `api`, starting with an Expo (React -Native) starter. The CLI treated an unknown kind as if it were not there: the alias resolver -skipped it, the prompts never offered it, and `verify` filtered it out without a word. - -A mobile starter is optional. `init` asks "Mobile app" after the backend, defaulting to none; -`--mobile=` (or the bare alias, `--mobile` / `--expo`) includes one; `--yes` scaffolds -without, since a native app brings prerequisites (an associated domain for passkeys) an -unattended run should not opt into; and a registry that predates the kind offers nothing, so -there is no question to ask. A chosen starter lands at `mobile/` with its `.env` filled from the -manifest, is recorded as `services.mobile` in `seamless.config.json`, is checked by `seamless -check` only when recorded, and is called out in the success output with how to start it and the -Android emulator host. `verify` announces the mobile templates it cannot drive instead of -filtering them silently. Template copying skips `.expo`, `ios`, and `android`. - -The templates registry pin moves to the release that carries the starter in a follow-up. diff --git a/.changeset/verify-pack-client-workspace.md b/.changeset/verify-pack-client-workspace.md deleted file mode 100644 index 4ef40e8..0000000 --- a/.changeset/verify-pack-client-workspace.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -'seamless-cli': patch ---- - -`seamless verify --local` packs `@seamless-auth/client` alongside `@seamless-auth/react` -when the React SDK checkout is an npm workspace. - -The client SDK repo is becoming a workspace that publishes a framework-agnostic -`@seamless-auth/client` next to `@seamless-auth/react`, and the react tarball depends on -the client one. Packing only the root of such a checkout would produce the private root -package, and installing the react tarball alone would go to the registry for a client -version that is not published yet. The harness now reads `workspaces` from the checkout's -`package.json`, packs both packages when it finds one, and the react image installs every -tarball in one `npm install` so the dependency resolves from the sibling file. A checkout -that predates the workspace is packed as before. The version line reported for -`@seamless-auth/react` reads the react package's own manifest in a workspace. diff --git a/CHANGELOG.md b/CHANGELOG.md index f0adbdb..7c252b2 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,42 @@ # seamless-cli +## 0.16.0 + +### Minor Changes + +- b9529c6: `seamless init` learns the `mobile` template kind. + + `seamless-templates` gains a third kind next to `web` and `api`, starting with an Expo (React + Native) starter. The CLI treated an unknown kind as if it were not there: the alias resolver + skipped it, the prompts never offered it, and `verify` filtered it out without a word. + + A mobile starter is optional. `init` asks "Mobile app" after the backend, defaulting to none; + `--mobile=` (or the bare alias, `--mobile` / `--expo`) includes one; `--yes` scaffolds + without, since a native app brings prerequisites (an associated domain for passkeys) an + unattended run should not opt into; and a registry that predates the kind offers nothing, so + there is no question to ask. A chosen starter lands at `mobile/` with its `.env` filled from the + manifest, is recorded as `services.mobile` in `seamless.config.json`, is checked by `seamless +check` only when recorded, and is called out in the success output with how to start it and the + Android emulator host. `verify` announces the mobile templates it cannot drive instead of + filtering them silently. Template copying skips `.expo`, `ios`, and `android`. + + The templates registry pin moves to the release that carries the starter in a follow-up. + +### Patch Changes + +- 4bbf7ac: `seamless verify --local` packs `@seamless-auth/client` alongside `@seamless-auth/react` + when the React SDK checkout is an npm workspace. + + The client SDK repo is becoming a workspace that publishes a framework-agnostic + `@seamless-auth/client` next to `@seamless-auth/react`, and the react tarball depends on + the client one. Packing only the root of such a checkout would produce the private root + package, and installing the react tarball alone would go to the registry for a client + version that is not published yet. The harness now reads `workspaces` from the checkout's + `package.json`, packs both packages when it finds one, and the react image installs every + tarball in one `npm install` so the dependency resolves from the sibling file. A checkout + that predates the workspace is packed as before. The version line reported for + `@seamless-auth/react` reads the react package's own manifest in a workspace. + ## 0.15.0 ### Minor Changes diff --git a/package.json b/package.json index 259e6a1..94f935c 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "seamless-cli", - "version": "0.15.0", + "version": "0.16.0", "description": "The Seamless Auth command-line interface", "homepage": "https://github.com/fells-code/seamless-cli#readme", "bugs": {