chore: bump @authorizerdev/authorizer-js to 3.3.0-rc.4#68
Merged
Conversation
Two breaking changes landed between rc.3 and rc.4: - #48 removed is_multi_factor_auth_enabled from SignUpRequest (security fix - closed a bypass of the server's MFA-on-by-default policy) - #50 flattened .webhooks()/.emailTemplates()/.verificationRequests() pagination params (PaginatedRequest -> PaginationRequest directly) Neither touches this package: it never sets is_multi_factor_auth_enabled on signup, and never imports AuthorizerAdmin or calls any of the three affected methods (grepped, confirmed zero matches both before and after the bump). tsc --noEmit and build both clean.
size-limit report 📦
|
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
1 participant
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.
Summary
Bump
@authorizerdev/authorizer-jsfrom3.3.0-rc.3to3.3.0-rc.4.Two breaking changes landed upstream between those versions:
is_multi_factor_auth_enabledfromSignUpRequest(security fix closing a bypass of the server's MFA-on-by-default policy). Scoped to the signup path only;UpdateProfileRequest/adminUpdateUserRequestkeep the field..webhooks()/.emailTemplates()/.verificationRequests()pagination params (PaginatedRequestwrapper removed,PaginationRequestused directly).Impact on this package
None. Confirmed via repo-wide grep both before and after the bump:
src/setsis_multi_factor_auth_enabledon the signup request (AuthorizerSignup.tsx'sSignUpRequestliteral doesn't include it).src/importsAuthorizerAdminor calls.webhooks()/.emailTemplates()/.verificationRequests()- those are admin-only methods this login-widget package never touches.Test plan
tsc --noEmitpassesnpm run buildpasses