Version Packages - #148
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-auth/react@0.12.0
Minor Changes
f59be34: Add a passkey while signed in, and say what a 401 at enrollment means.
registerPasskeyis now onuseAuth()and on the framework-agnostic session actions,not only on the client. The bundled UI already told users they could "add a passkey later
from a device that does", and nothing in the package implemented that:
credentialscouldbe listed and deleted but never added. The context version refreshes the session
afterwards, so a settings screen renders the new passkey without a reload.
Enrollment now requires a signed-in session, which is a coordinated change with
seamless-auth-apiand the server adapters. Upgrade all three together: the auth API andthe adapter have no safe release order between them, and enrollment answers
401untilboth land. The signup flow already satisfies it, because
verifying the email OTP issues a session before the passkey screen is reached, so nothing
in the bundled views moves. An application that called
registerPasskey()beforeverifying an address has to move that call after it.
A 401 from enrollment now reads "Your session expired before the passkey was saved" rather
than the generic "Error registering passkey." It is the session rather than anything about
the authenticator, and the generic wording invited the user to retry with the same expired
one.
isUnauthenticated(error)is exported for callers rendering their own screens.Corrects a stale README example that still passed a
tokentoregisterPasskey, a fieldremoved when the wire contract moved to
@seamless-auth/types.