Repository navigation
Version Packages (next) - #136
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
November 1, 2026 00:40
b25b556 to
69d3ee3
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
November 1, 2026 00:41
69d3ee3 to
7890c18
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.
mainis currently in pre mode so this branch has prereleases rather than normal releases. If you want to exit prereleases, runchangeset pre exitonmain.Releases
@seamless-auth/types@0.34.0-next.4
Minor Changes
9964761: Add the
oidc_backchannel_logout_sentandoidc_backchannel_logout_failedauth event types, which the API writes for each back-channel logout token it delivers or fails to deliver (feat(oidc): send back-channel logout when a provider sign-in's session ends seamless-auth-api#536).c8fe306:
EmailMessageSchemaaccepts an optionalheadersrecord of string names to string values, such asList-UnsubscribeandList-Unsubscribe-Postfor one-click unsubscribe. The inferredEmailMessagetype gains the optionalheadersfield.@seamless-auth/messagingalready sends these through SES v2 and validates the names and values there.New
SendEnrollmentInviteEmailInputSchemaandSendEnrollmentInviteEmailInput: the input for the email that asks a user to sign in and add a passkey.signInUrlis the application's normal sign-in page and carries no credential.0e00355: OpenID Provider applications gain
pkceRequired,trueby default. Only a confidential client may set it tofalse(RFC 9700 section 2.1.1);checkOidcApplicationrefuses the opt-out on a public client.OidcClientMetadatagains optionalurn:seamless:pkce_required, sent asfalseonly for an opted-out client, which must then sendnoncewhenever it asks for an ID token. Applications also gainnonceRequired,trueby default, which may be turned off only once PKCE is waived;urn:seamless:nonce_requiredcarries it to the edge. Adds theadmin_oidc_application_pkce_updatedandadmin_oidc_application_nonce_updatedauth events.0e00355:
OidcClientMetadatagains optionalurn:seamless:access_token_ttl,urn:seamless:id_token_ttlandurn:seamless:refresh_token_ttl(seconds), the application'saccessTokenTtlSeconds,idTokenTtlSecondsandrefreshTokenTtlSeconds. Absent means the provider's default. The OpenID Provider service applies them, and an access token for a resource with its own lifetime takes the shorter one.97b5c18: Add
OidcPayloadConsumeResponseSchema({ consumed: boolean }) forPOST /oidc/payloads/:model/:id/consume, which now answers200instead of204.consumedis true only for the caller whose request marked the record consumed, so of two concurrent refreshes with the same token exactly one wins, and the OpenID Provider service treats the other as reuse.663d947:
OidcSignRequestgainsgrantType(OidcUserGrantTypeSchema:authorization_codeorurn:ietf:params:oauth:grant-type:device_code), required forid_tokenandaccess_tokenand refused forclient_credentials. It names the grant the user's authorization was made with, and a refresh names the grant it continues, so the API can refuseacron device-flow tokens (ADR 0001, D10).OIDC_EDGE_CONTRACT_VERSIONis now 2: the OpenID Provider service and the API must both move to this release, since an edge on version 1 refuses to start against an API on version 2.