Repository navigation
chore: version packages - #257
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
9 times, most recently
from
October 9, 2026 15:32
4650db0 to
66117e7
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 9, 2026 15:52
66117e7 to
f258cab
Compare
11 of 13 tasks
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.22.0
Minor Changes
seamless initnow writes a rootAGENTS.mdand aCLAUDE.md(See @AGENTS.md) besidedocker-compose.ymlandseamless.config.json. The guide is built from the choices init made: the directory and template each starter came from (linking its ownAGENTS.md), how the auth server runs, the admin console, the ports, how to start the stack, the owner email that becomes the first admin, and the rules for agents (use the SDK and adapter, never your own JWT, password, session cookie or login endpoint code), plus a link to https://docs.seamlessauth.com/llms.txt.seamless addnow wires Go (net/http, Gin, chi, Echo), Rust (Axum) and Python (FastAPI, Django) backends on the seamless-auth-go, seamless-auth crate and seamless-auth PyPI adapters. It reads go.mod, Cargo.toml, pyproject.toml or requirements.txt, installs withgo get,cargo add,uv addorpoetry add(printing thepip installfor a plain pip project), says how the language loads.env, and prints the code for that framework, including the development-only code logging and the admin console mount.seamless addnow wires Angular, Vue and SvelteKit web apps on the@seamless-auth/angular,@seamless-auth/vueand@seamless-auth/sveltebindings, alongside React. It installs the binding (andvue-routeror@angular/routerwhen the app has no router), writesVITE_API_URLfor Vue and SvelteKit, and prints the code for each file: the provider or plugin, the bundled sign-in screens as routes, and guards for signed-in and signed-out pages. Angular, which does not read.env, gets the backend URL in the printed config. Nuxt and Svelte without SvelteKit are reported rather than wired.seamless add, which adds Seamless Auth to an existing Express or Fastify backend and React web app. It connects a local auth server (written toseamless/) or a managed application, writes the backend's.envand the web app's API URL while keeping existing values, installs the adapter and SDK with the project's package manager, and prints the code to add for TypeScript or JavaScript. It never edits source files. Commands now run without a shell outside Windows, which also stops Node 24's DEP0190 warning.seamless verifynow drives an Angular app through the same browser specs as the React template. Theangularandangular-devlayers run the reference app inverify/angular-appon@seamless-auth/angular(production build, andng servewith--dev), or an Angular web template once the registry has one.SEAMLESS_ANGULAR_DIRpoints the run at another Angular app, and--localinstalls the locally built@seamless-auth/clientand@seamless-auth/angular.seamless verifynow drives a SvelteKit app through the same browser specs as the React template. Thesvelteandsvelte-devlayers run the reference app inverify/svelte-appon@seamless-auth/svelte(SvelteKit 3 as a single-page app, as a production build and onvite devwith--dev), or a Svelte web template once the registry has one.SEAMLESS_SVELTE_DIRpoints the run at another Svelte app, and--localinstalls the locally built@seamless-auth/clientand@seamless-auth/svelte.seamless verifynow drives a Vue app through the same browser specs as the React template. Thevueandvue-devlayers run the reference app inverify/vue-appon@seamless-auth/vue(a production build, andvitewith--dev), or a Vue web template once the registry has one.SEAMLESS_VUE_DIRpoints the run at another Vue app, and--localinstalls the locally built@seamless-auth/clientand@seamless-auth/vue.Patch Changes
@seamless-auth/clientsend them. v0.18.0 still serves the deprecated GET routes, so projects on the Express and Fastify starters keep working. The next steps afterseamless initnow give each api starter its own command (go run .,cargo run,uv run uvicorn ...) instead ofnpm install && npm run dev.seamless-templatesv0.18.0(wasv0.17.0). Every starter now ships anAGENTS.mdand aCLAUDE.md, so the root guideseamless initwrites links each starter'sAGENTS.mdinstead of its README, and the Go (Gin), Rust (Axum) and Python (FastAPI) api starters are available asbeta.initauth server prompt, and describe the package as the CLI for Seamless Auth, open source passwordless auth.seamless verifynow waits for each browser service's healthcheck before running its specs. Thevue-devandsvelte-devservices compile their app at startup and report healthy only once a compiled module and the prebundled SDK are served, so a cold Vite dev server no longer makes the first browser spec time out on a slow runner. The production web services' healthchecks now probe 127.0.0.1, since nginx listens on IPv4 only and they never passed onlocalhost. A service that never becomes healthy fails its own layer, with its recent logs, and the run continues.