Version Packages - #69
Open
github-actions[bot] wants to merge 1 commit into
Open
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/types@0.22.0
Minor Changes
c934d8f: Add
flow_rate_limitsto the system config, and pin the Android WebAuthn origin form.seamless-auth-apilimits how often one caller may start an OTP, magic link, or OAuth flow, ontop of the general
rate_limit, with constants fixed in code: 10 OTP sends and 20 magic links perIP per 15 minutes, 5 per address, 30 OAuth starts per IP and 10 per provider. Those are fine for a
web audience and wrong for a mobile one, because carriers put thousands of subscribers behind one
address.
flow_rate_limitsis an object key (windowSeconds,otp.perIp,otp.perIdentity,magicLink.perIp,magicLink.perIdentity,oauth.perIp,oauth.perProvider) whose defaultsare exactly those constants, so a deployment that sets nothing behaves as it did, and a partial
value fills the flows it leaves out.
FlowRateLimitsSchema,FlowRateLimitsandDefaultFlowRateLimitsare exported; the patch schema accepts the key.originsgains a test and a comment for the form Android reports,android:apk-key-hash:<base64url>,which
z.url()accepts as an opaque URL. It has to keep accepting it for native passkeys toverify, and nothing said so until now.
Part of the mobile track, [Epic] React Native mobile template seamless-templates#40.