chore: scaffold from seamless-templates v0.15.0 - #206
Merged
Conversation
SEAMLESS_TEMPLATES_REF v0.14.0 to v0.15.0, and the conformance harness adapters to @seamless-auth/express ^0.16.0 and @seamless-auth/fastify ^0.7.0. Templates v0.15.0 is the release that carries the Expo starter the mobile template kind in 0.16.0 was written for. Against v0.14.0 the registry has no mobile kind, so init never asked and --mobile=expo was refused as an unknown option; against v0.15.0 the starter scaffolds at mobile/ with EXPO_PUBLIC_API_URL filled from the manifest. The API starters in the same release move to the adapters that accept bearer access tokens and pass authServerUrl and audience into requireAuth, which is why the harness adapters move with them.
This was referenced Sep 13, 2026
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
1 participant
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.
Summary
SEAMLESS_TEMPLATES_REFmoves fromv0.14.0tov0.15.0, the templates release that carries the Expo starter and themobilekind. This is the follow-up the 0.16.0 notes promised: againstv0.14.0the registry has no mobile kind, soinitnever asked and--mobile=expowas refused as an unknown option.@seamless-auth/express^0.16.0and@seamless-auth/fastify^0.7.0, the versions thev0.15.0API starters ship, as the previous pin moves did.minor, matching earlier ecosystem bumps.The auth API (
v0.13.1) and admin dashboard (v0.7.0) pins do not move. Templatesv0.15.0leaves the web starters on@seamless-auth/react0.12.0; the only registry change is the newexpoentry.Part of fells-code/seamless-templates#40.
Verification
npm run build,npm test(1019 passed, 4 skipped), and the pre-commit coverage run, all green.init new --local --yes --mobile=expo --auth=docker --admin=noneagainst the new pin: scaffoldsweb/,api/(on@seamless-auth/express^0.16.0), andmobile/(on@seamless-auth/react-native^0.1.0) withEXPO_PUBLIC_API_URL=http://localhost:3000inmobile/.env,services.mobilerecorded inseamless.config.json, and the mobile block in the success output.SEAMLESS_TEMPLATES_REF=v0.14.0reproduces the pre-bump behaviour:Error: Unknown option "--expo".v0.15.0registry and archive, so it exercises the new pin in CI.