diff --git a/.changeset/bump-adapter-express-pin.md b/.changeset/bump-adapter-express-pin.md deleted file mode 100644 index 875a36e..0000000 --- a/.changeset/bump-adapter-express-pin.md +++ /dev/null @@ -1,7 +0,0 @@ ---- -"seamless-cli": patch ---- - -Bump the verify adapter to `@seamless-auth/express@^0.6.0` (the stable release that includes the -registration-session and non-JSON-response fixes), so the released conformance run tests against -the current published packages. diff --git a/.changeset/conformance-repoint.md b/.changeset/conformance-repoint.md deleted file mode 100644 index 41e69cd..0000000 --- a/.changeset/conformance-repoint.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"seamless-cli": patch ---- - -Point the conformance harness at the seamless-templates monorepo. `seamless verify` now resolves the React web template from `../seamless-templates/templates/web/react-vite` by default (still overridable with `SEAMLESS_REACT_DIR`), and the reusable `verify-conformance.yml` workflow checks out `seamless-templates` (input `templates-ref`) instead of the standalone starter repo. diff --git a/.changeset/init-example-flags.md b/.changeset/init-example-flags.md deleted file mode 100644 index 016eace..0000000 --- a/.changeset/init-example-flags.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"seamless-cli": minor ---- - -`seamless init --` selects a use-case starter by its registry alias (e.g. `seamless init --oauth`), skipping the web prompt. Aliases are defined in the templates registry, so adding an example needs no CLI change. Unknown flags list the available examples, and the interactive web prompt now presents the available examples. diff --git a/.changeset/registry-driven-templates.md b/.changeset/registry-driven-templates.md deleted file mode 100644 index 944c481..0000000 --- a/.changeset/registry-driven-templates.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"seamless-cli": minor ---- - -Scaffold web and api starters from the seamless-templates registry instead of hardcoded per-framework generators. The CLI now reads the registry to build its prompts, downloads the selected templates from the templates monorepo at a pinned ref, and applies each template's env contract. Adding a new framework is a templates-repo change, not a CLI change. Set SEAMLESS_TEMPLATES_DIR to scaffold from a local checkout, or SEAMLESS_TEMPLATES_REF to pin a different ref. diff --git a/.changeset/verify-multi-template.md b/.changeset/verify-multi-template.md deleted file mode 100644 index 703c652..0000000 --- a/.changeset/verify-multi-template.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"seamless-cli": minor ---- - -`seamless verify` now conformance-tests every web template in the registry. It runs the API and adapter layers once, then builds, serves, and drives each web template in turn, scoping the browser suite to the flows the template's manifest declares (`verify.flows`, e.g. `["oauth"]`). React specs are tagged by feature (`@login`, `@oauth`) so a template runs only its relevant flows; a template with no declared flows runs the full suite. `SEAMLESS_REACT_DIR` still overrides with a single template. diff --git a/.changeset/verify-registry-web.md b/.changeset/verify-registry-web.md deleted file mode 100644 index 1230d08..0000000 --- a/.changeset/verify-registry-web.md +++ /dev/null @@ -1,5 +0,0 @@ ---- -"seamless-cli": patch ---- - -`seamless verify` now resolves the web template to conformance-test from the seamless-templates registry (the first runnable web template) instead of a hardcoded path. SEAMLESS_REACT_DIR still overrides with a direct template path, and SEAMLESS_TEMPLATES_DIR points at a local templates checkout. Running the browser suite against every web template is a follow-up. diff --git a/CHANGELOG.md b/CHANGELOG.md index 5cdf38d..c8e67e4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,21 @@ # seamless-cli +## 0.4.0 + +### Minor Changes + +- 7409238: `seamless init --` selects a use-case starter by its registry alias (e.g. `seamless init --oauth`), skipping the web prompt. Aliases are defined in the templates registry, so adding an example needs no CLI change. Unknown flags list the available examples, and the interactive web prompt now presents the available examples. +- fcac569: Scaffold web and api starters from the seamless-templates registry instead of hardcoded per-framework generators. The CLI now reads the registry to build its prompts, downloads the selected templates from the templates monorepo at a pinned ref, and applies each template's env contract. Adding a new framework is a templates-repo change, not a CLI change. Set SEAMLESS_TEMPLATES_DIR to scaffold from a local checkout, or SEAMLESS_TEMPLATES_REF to pin a different ref. +- 27a6ec1: `seamless verify` now conformance-tests every web template in the registry. It runs the API and adapter layers once, then builds, serves, and drives each web template in turn, scoping the browser suite to the flows the template's manifest declares (`verify.flows`, e.g. `["oauth"]`). React specs are tagged by feature (`@login`, `@oauth`) so a template runs only its relevant flows; a template with no declared flows runs the full suite. `SEAMLESS_REACT_DIR` still overrides with a single template. + +### Patch Changes + +- fbcc17e: Bump the verify adapter to `@seamless-auth/express@^0.6.0` (the stable release that includes the + registration-session and non-JSON-response fixes), so the released conformance run tests against + the current published packages. +- 57c7819: Point the conformance harness at the seamless-templates monorepo. `seamless verify` now resolves the React web template from `../seamless-templates/templates/web/react-vite` by default (still overridable with `SEAMLESS_REACT_DIR`), and the reusable `verify-conformance.yml` workflow checks out `seamless-templates` (input `templates-ref`) instead of the standalone starter repo. +- c41e68b: `seamless verify` now resolves the web template to conformance-test from the seamless-templates registry (the first runnable web template) instead of a hardcoded path. SEAMLESS_REACT_DIR still overrides with a direct template path, and SEAMLESS_TEMPLATES_DIR points at a local templates checkout. Running the browser suite against every web template is a follow-up. + ## 0.3.0 ### Minor Changes diff --git a/package.json b/package.json index fa6fb0d..0bd4e79 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "seamless-cli", - "version": "0.3.0", + "version": "0.4.0", "description": "The Seamless Auth command-line interface", "homepage": "https://github.com/fells-code/seamless-cli#readme", "bugs": {