Repository navigation
Version Packages - #109
Merged
Merged
Version Packages#109
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2026 14:59
5128bf6 to
ecb746c
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
@seamless-auth/types@0.30.0
Minor Changes
9f1b524: Schemas for the v0.20 recovery and staged policy work in seamless-auth-api.
RecoveryCodeSchema,RecoveryCodesStatusSchema,RecoveryCodesGeneratedSchema,RecoveryCodeRedeemRequestSchema.AccountRecoveryStartRequestSchema,AccountRecoveryVerifyRequestSchema,AccountRecoveryStatusSchema,AccountRecoveryCancelRequestSchemaand friends.RecoverySessionResponseSchemafor the restricted session a recovery issues (recovery: true,nextStep: 'enroll_passkey'). Session responses gain an optionalrecoveryflag.POLICY_KEYS,PolicyDocumentSchema,PolicyVersionSchema,PolicyDraftSchema,PolicyStateResponseSchema, publish, rollback and versions schemas, andPolicyDryRunRequestSchema/PolicyDryRunResponseSchema.recovery_codes(on by default) andaccount_recovery(off by default, 24h delay, 1h to 30d), both patchable.PublicSystemConfigResponseSchemagains optionalrecoveryCodesandaccountRecovery.All additions are optional or defaulted, so existing payloads still parse.
96136fc: OAuth provider config holds the rules the auth server enforces since 0.19.4 (GHSA-qx82-28gf-w744), so the dashboard and CLI refuse a bad provider before the API does.
clientSecretEnvmust be an env var name ending in_CLIENT_SECRET(newOAuthClientSecretEnvSchema).authorizationUrl,tokenUrl,userInfoUrlandjwksUrimust usehttporhttps.z.url()alone accepted any scheme, includingjavascript:. The server still requireshttpsin production.Breaking for a stored provider that names another env var or uses another scheme: it now fails
OAuthProviderConfigSchema, as it already fails on API 0.19.4.