chore: version packages - #87
Merged
Merged
Conversation
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-templates@0.13.0
Minor Changes
4fd56e9: Move the starters onto the auth packages that put passkey enrolment behind a
session.
@seamless-auth/reactgoes from 0.11.0 to 0.12.0 in both React starters,@seamless-auth/expressfrom 0.13.0 to 0.14.0, and@seamless-auth/fastifyfrom 0.4.0 to 0.5.0.
These three are one release.
/webAuthn/register/startand/webAuthn/register/finishused to accept the ephemeral token the auth API mintsfrom an email address alone, so anyone who knew an address could enrol a
credential against that account and sign in as its owner. Both routes now read
the access session instead. The auth API stopped accepting the old token in
0.11.0, and there is no safe order between the two sides: an older adapter sends
what the API refuses, and these adapters send what an older API refuses, so
enrolment answers 401 until both have landed. Point a scaffolded project at
seamless-auth-api0.12.0, the current release.No shipped flow loses a step. Registration proves an address with an email OTP
and verifying it issues a session, so the client already holds one by the time
the passkey screen appears. An application built on an older starter that offered
enrolment before verifying an address has to move that call after it.
The starters needed the version and nothing else.
createSeamlessAuthServer,requireAuth,requireRoleandSeamlessAuthUserare unchanged, and theadapters' other work in 0.14.0 and 0.5.0 is route plumbing behind them: a
DELETE /admin/organizations/:organizationIdproxy, and the query stringrestored on
GET /admin/usersand the login-stats endpoint.The React bump also adds capability the starters do not use yet.
registerPasskeyis now on
useAuth(), so a settings screen can add a passkey to a signed-inaccount rather than only listing and deleting, and
isUnauthenticated(error)isexported for callers rendering their own enrolment screens.