From bc3f1d2b9501e90bf2ac9d3c65d0b461166c2b96 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" <41898282+github-actions[bot]@users.noreply.github.com> Date: Sun, 2 Aug 2026 22:05:43 +0000 Subject: [PATCH] chore: version packages --- .changeset/postgres-18-volume-mount.md | 22 ----------- .changeset/postgres-18.md | 16 -------- .changeset/verify-fastify-adapter.md | 17 --------- CHANGELOG.md | 52 ++++++++++++++++++++++++++ package.json | 2 +- 5 files changed, 53 insertions(+), 56 deletions(-) delete mode 100644 .changeset/postgres-18-volume-mount.md delete mode 100644 .changeset/postgres-18.md delete mode 100644 .changeset/verify-fastify-adapter.md diff --git a/.changeset/postgres-18-volume-mount.md b/.changeset/postgres-18-volume-mount.md deleted file mode 100644 index 4a814f2..0000000 --- a/.changeset/postgres-18-volume-mount.md +++ /dev/null @@ -1,22 +0,0 @@ ---- -"seamless-cli": patch ---- - -Fix the scaffolded database failing to start on PostgreSQL 18. - -The PostgreSQL 18 bump moved the image tag but not the volume mount. PostgreSQL 18+ images store data -in a major-versioned subdirectory (`/var/lib/postgresql/18/docker`), so a mount at -`/var/lib/postgresql/data` is ignored and the container refuses to start, restart-looping on: - -``` -Error: in 18+, these Docker images are configured to store database data in a - format which is compatible with "pg_ctlcluster" ... - Counter to that, there appears to be PostgreSQL data in: - /var/lib/postgresql/data (unused mount/volume) -``` - -The generated `docker-compose.yml` now mounts `pgdata:/var/lib/postgresql`. See -docker-library/postgres#1259. - -This only ever affected projects scaffolded from the unreleased PostgreSQL 18 change, so no published -version of the CLI produced a broken scaffold. diff --git a/.changeset/postgres-18.md b/.changeset/postgres-18.md deleted file mode 100644 index daf80a7..0000000 --- a/.changeset/postgres-18.md +++ /dev/null @@ -1,16 +0,0 @@ ---- -"seamless-cli": minor ---- - -Scaffold new projects on PostgreSQL 18, and run the conformance harness on it too. - -`seamless init` generated a stack pinned to `postgres:17` while the verify harness ran `postgres:16`. -Both are now `postgres:18`, so what the harness certifies is the major a fresh scaffold actually -gets. - -This does not touch an existing project. The image is written into each scaffold's own -`docker-compose.yml` at generation time, so a project keeps whatever major it was scaffolded with and -its data directory is never pulled out from under it. Only newly scaffolded projects get 18, on a -fresh volume. Upgrading an existing project is a deliberate act: change the image in its -`docker-compose.yml`, and dump and restore the volume, since PostgreSQL will not start against a data -directory written by a different major. diff --git a/.changeset/verify-fastify-adapter.md b/.changeset/verify-fastify-adapter.md deleted file mode 100644 index c0aba3a..0000000 --- a/.changeset/verify-fastify-adapter.md +++ /dev/null @@ -1,17 +0,0 @@ ---- -"seamless-cli": minor ---- - -`seamless verify` now exercises the Fastify starter. The scaffold has offered a Fastify API since the -templates bump, but the conformance harness only ever drove the Express adapter, so a green run said -nothing about whether a Fastify-scaffolded project actually worked. - -The stack gains a second adopter backend (`verify/adapter-fastify-app`, on port 3001) built on -`@seamless-auth/fastify`, a twin of the Express one: same routes, same env contract, same capture -transport. The existing adapter specs run against both without being duplicated, since the two -Playwright projects share a test directory and differ only in which backend they point at. The -conformance grid gains an `adapter-fastify` column, so a failure in one framework is attributable to -that framework. - -`--api-only` and `--no-react` are unchanged, and `--local` builds and packs `@seamless-auth/fastify` -from source alongside core and express. diff --git a/CHANGELOG.md b/CHANGELOG.md index 102434a..bae0d97 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -1,5 +1,57 @@ # seamless-cli +## 0.12.0 + +### Minor Changes + +- 35d9f3e: Scaffold new projects on PostgreSQL 18, and run the conformance harness on it too. + + `seamless init` generated a stack pinned to `postgres:17` while the verify harness ran `postgres:16`. + Both are now `postgres:18`, so what the harness certifies is the major a fresh scaffold actually + gets. + + This does not touch an existing project. The image is written into each scaffold's own + `docker-compose.yml` at generation time, so a project keeps whatever major it was scaffolded with and + its data directory is never pulled out from under it. Only newly scaffolded projects get 18, on a + fresh volume. Upgrading an existing project is a deliberate act: change the image in its + `docker-compose.yml`, and dump and restore the volume, since PostgreSQL will not start against a data + directory written by a different major. + +- d5da781: `seamless verify` now exercises the Fastify starter. The scaffold has offered a Fastify API since the + templates bump, but the conformance harness only ever drove the Express adapter, so a green run said + nothing about whether a Fastify-scaffolded project actually worked. + + The stack gains a second adopter backend (`verify/adapter-fastify-app`, on port 3001) built on + `@seamless-auth/fastify`, a twin of the Express one: same routes, same env contract, same capture + transport. The existing adapter specs run against both without being duplicated, since the two + Playwright projects share a test directory and differ only in which backend they point at. The + conformance grid gains an `adapter-fastify` column, so a failure in one framework is attributable to + that framework. + + `--api-only` and `--no-react` are unchanged, and `--local` builds and packs `@seamless-auth/fastify` + from source alongside core and express. + +### Patch Changes + +- 5cb6911: Fix the scaffolded database failing to start on PostgreSQL 18. + + The PostgreSQL 18 bump moved the image tag but not the volume mount. PostgreSQL 18+ images store data + in a major-versioned subdirectory (`/var/lib/postgresql/18/docker`), so a mount at + `/var/lib/postgresql/data` is ignored and the container refuses to start, restart-looping on: + + ``` + Error: in 18+, these Docker images are configured to store database data in a + format which is compatible with "pg_ctlcluster" ... + Counter to that, there appears to be PostgreSQL data in: + /var/lib/postgresql/data (unused mount/volume) + ``` + + The generated `docker-compose.yml` now mounts `pgdata:/var/lib/postgresql`. See + docker-library/postgres#1259. + + This only ever affected projects scaffolded from the unreleased PostgreSQL 18 change, so no published + version of the CLI produced a broken scaffold. + ## 0.11.0 ### Minor Changes diff --git a/package.json b/package.json index 34b0862..9d2b696 100644 --- a/package.json +++ b/package.json @@ -1,6 +1,6 @@ { "name": "seamless-cli", - "version": "0.11.0", + "version": "0.12.0", "description": "The Seamless Auth command-line interface", "homepage": "https://github.com/fells-code/seamless-cli#readme", "bugs": {