chore: version packages - #163
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 2, 2026 20:19
a1e2336 to
72d15ef
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 2, 2026 22:05
72d15ef to
bc3f1d2
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
seamless-cli@0.12.0
Minor Changes
35d9f3e: Scaffold new projects on PostgreSQL 18, and run the conformance harness on it too.
seamless initgenerated a stack pinned topostgres:17while the verify harness ranpostgres:16.Both are now
postgres:18, so what the harness certifies is the major a fresh scaffold actuallygets.
This does not touch an existing project. The image is written into each scaffold's own
docker-compose.ymlat generation time, so a project keeps whatever major it was scaffolded with andits 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 datadirectory written by a different major.
d5da781:
seamless verifynow exercises the Fastify starter. The scaffold has offered a Fastify API since thetemplates 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 capturetransport. 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-fastifycolumn, so a failure in one framework is attributable tothat framework.
--api-onlyand--no-reactare unchanged, and--localbuilds and packs@seamless-auth/fastifyfrom 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/datais ignored and the container refuses to start, restart-looping on:The generated
docker-compose.ymlnow mountspgdata:/var/lib/postgresql. SeeChange
PGDATAin 18+ to/var/lib/postgresql/MAJOR/dockerdocker-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.