Repository navigation
chore: version packages - #257
Open
github-actions[bot] wants to merge 1 commit into
Open
github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
October 8, 2026 23:34
016a13e to
0a85c54
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 9, 2026 00:37
0a85c54 to
2b787bf
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
[email protected]
Minor Changes
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 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.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.