Skip to content

chore(deps): update @seamless-auth/types to 0.31.0 - #210

Merged
Bccorb merged 1 commit into
mainfrom
chore/types-0-31
Oct 25, 2026
Merged

Bccorb merged 1 commit into
mainfrom
chore/types-0-31

Conversation

@Bccorb

@Bccorb Bccorb commented Oct 25, 2026

Copy link
Copy Markdown
Contributor

The Check @seamless-auth/types is current CI step fails on main and on every open PR, because 0.31.0 (the auth server v0.20 contract) is published and client, react and react-native pin ^0.29.0.

This is the bump alone, with no code changes, so it can merge first and unblock #209 and the v0.20 recovery features PR.

Checks on this branch: npm run lint, typecheck, format:check and build all exit 0. check:types-current reports current. npm test -- --runInBand: Jest 618 passed, Vitest 3 files passed.

@Bccorb
Bccorb merged commit dc52b23 into main Oct 25, 2026
5 checks passed
@Bccorb
Bccorb deleted the chore/types-0-31 branch October 25, 2026 14:50
Bccorb added a commit that referenced this pull request Oct 26, 2026
…ement (#211)

* fix(deps): require @seamless-auth/types 0.31.0 for account recovery

* feat(client): recovery codes, account recovery and recovery sessions

Add client methods for the auth API v0.20 recovery routes, the bearer
route rules that mirror their adapter manifest credentials, and the
shared flows the bundled screens of every binding build on.

A session issued by a recovery code or a completed account recovery is
tracked by the client and mirrored into the session state. After a
passkey or TOTP enrollment made from it, the client refreshes the
session so the new access token no longer carries the recovery claim.

* chore: drop the types bump changeset, which ships with #210

* feat(react): recovery screens in AuthRoutes

Add the sign-in side of account recovery to the prebuilt UI:

- /recovery-code signs in with a recovery code
- /recovery-codes generates and shows a first set after a passkey is
  enrolled, and asks the user to confirm they saved it
- /account-recovery runs self-service recovery: channel, code, the
  waiting period, then completion
- /recovery/cancel takes the token from the notice link's fragment,
  drops it from the address bar and cancels the request

The sign-in screen offers recovery only where the public configuration
reports it, and a recovery session goes straight to passkey enrollment,
which it cannot skip.

Refs #185, #208

* docs: recovery codes, account recovery and passkey management

* feat(react): passkey and recovery sections for account settings

Export router-free settings sections built on the public primitives:

- PasskeyManagement lists passkeys with name, kind and last use, renames
  and deletes them, adds another, and asks for a second passkey when
  there is only one
- RecoveryCodeSettings shows the codes left and generates or replaces a
  set, stepping up with the passkey when the API asks for it
- RecoveryRequests lists open account recovery requests with cancel
- AccountSecurity renders all three

Refs #185, #186, #208

* feat(svelte): expose the recovery session actions

* style: format the types 0.31.0 changeset

---------

Co-authored-by: Brandon Corbett <Bccorb@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant