fix(deps): update dependency @simplewebauthn/browser to v14 - #689
Open
renovate[bot] wants to merge 3 commits into
Open
renovate[bot] wants to merge 3 commits into
renovate[bot] wants to merge 3 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
renovate
Bot
force-pushed
the
renovate/simplewebauthn-browser-14.x
branch
from
September 10, 2026 16:01
bb0a22a to
ae39d95
Compare
renovate
Bot
force-pushed
the
renovate/simplewebauthn-browser-14.x
branch
from
September 19, 2026 20:05
ae39d95 to
d1697d9
Compare
* Allow HackPSU's own Cloud Run origins to authenticate (#705) Gavel now runs on Cloud Run at gavel-production-695455897614.us-east4.run.app. That origin was not in the allowlist, so resolveReturnTo discarded it and sent users to hackpsu.org instead -- login could start but never come back. Scoped to our project rather than to .run.app as a whole. Cloud Run derives its hostname as <service>-<project-number>.<region>.run.app, so the project number identifies the owner; allowing .run.app outright would let anyone deploy a service and have buildReturnUrl hand it a session token, which is the same class of problem resolveReturnTo exists to prevent. A service in another project cannot forge it: naming theirs foo-695455897614 yields foo-695455897614-<their-number>.<region>.run.app, whose first label ends with their number, not ours. The number is overridable via CLOUD_RUN_PROJECT_NUMBER. Classified as staging rather than falling through to local, because Cloud Run is a real HTTPS deployment whose cookies must be marked Secure, but is not on hackpsu.org so it cannot read the shared session cookie and has to use the token handoff -- exactly what staging already means here. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> * chore(deps): update dependency zod to v4.6.5 --------- Co-authored-by: Kanishk Sachdev <64576646+kensac@users.noreply.github.com> Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com> Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
renovate
Bot
force-pushed
the
renovate/simplewebauthn-browser-14.x
branch
from
September 20, 2026 21:28
d1697d9 to
e8652e2
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 contains the following updates:
^13.1.2→^14.0.0Release Notes
MasterKale/SimpleWebAuthn (@simplewebauthn/browser)
v14.0.0Compare Source
The headlining feature of this release is @simplewebauthn/server gaining support for passkeys
using the ML-DSA-44, ML-DSA-65, and ML-DSA-87 PQC algorithms in supported runtimes. And in those
same supported runtimes, SimpleWebAuthn will automatically encourage registration of ML-DSA-44
passkeys to future-proof Relying Parties as PQC-capable FIDO2 authenticators and credential managers
start coming to market. See https://simplewebauthn.dev/docs/advanced/server/pqc-ml-dsa-support for
more info 🚀
Setting our sites on the browser, @simplewebauthn/browser picks up a new
sendSignal()methodas a single method to call all of the
WebAuthn Signal APIs. See
https://simplewebauthn.dev/docs/packages/browser#sendsignal for more info 🛜
As for breaking changes, the minimum supported version of Node has been raised to Node LTS 22.x
and higher, and Deno v2.4.x and higher. Going forward, SimpleWebAuthn will more formally aim
to support Node LTS releases through their Active and Maintenance windows as tracked on
the Node.js Releases page, and aim to support Deno
minor releases for up to one year after their release
That's not all, though. Continue reading for the full list of changes in this release! 🎉
Changes:
passkey public key algorithms when the runtime supports them. In runtimes that support these PQC
algorithms,
generateRegistrationOptions()will include ML-DSA-44 as the most preferred publickey algorithm during registration. See
https://simplewebauthn.dev/docs/advanced/server/pqc-ml-dsa-support for more info
(#785,
#794)
sendSignal()method offers a simple way to invoke theWebAuthn Signal APIs. See
https://simplewebauthn.dev/docs/packages/browser#sendsignal for more info
(#778)
browserSupportsPasskeys()helper method performs more robust WebAuthnsupport detection by also checking for typical passkey-related WebAuthn features. See
https://simplewebauthn.dev/docs/packages/browser#browsersupportspasskeys for more info
(#761)
getBrowserCapabilities()helper method wraps WebAuthn'sgetClientCapabilities()with additional feature detection checks when possible. Seehttps://simplewebauthn.dev/docs/packages/browser#getbrowsercapabilities for more info
(#761)
verifyAuthenticationResponse()accepts an optional newexpectedTopOriginargumentthat supports cross-origin authentication verification. See
https://simplewebauthn.dev/docs/advanced/server/cross-origin-support for more info
(#773)
MetadataService.initialize()accepts an optional newloggerargument that can beused to capture MetadataService status output in a project-specific manner. See
https://simplewebauthn.dev/docs/advanced/server/metadata-service#logging for more info
(#765)
transportsinexcludeCredentialswhen callinggenerateRegistrationOptions(), andallowCredentialswhen callinggenerateAuthenticationOptions(), has been updated tostring[]to make it easier to call thesemethods (#776)
"tpm"attestation verification is now more tolerant of variable casing in the TPMmanufacturer IDs (#772)
generateRegistrationOptions()andverifyRegistrationResponse()now use the samedefault list of allowed public key algorithms for
supportedAlgorithmIDs(#791)
validateCertificatePath()helper now supports x5c arrays containingcross-signed certificates (#796)
Breaking Changes
and higher, and Deno v2.4.x and higher
(#763)
Configuration
📅 Schedule: (in timezone America/New_York)
* 0-23 * * *)🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.