Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update module github.com/go-webauthn/webauthn to v0.11.2 #45

Closed
wants to merge 1 commit into from

Conversation

descope[bot]
Copy link
Contributor

@descope descope bot commented Sep 15, 2024

This PR contains the following updates:

Package Type Update Change
github.com/go-webauthn/webauthn require minor v0.10.2 -> v0.11.2

Release Notes

go-webauthn/webauthn (github.com/go-webauthn/webauthn)

v0.11.2

Compare Source

Bug Fixes

v0.11.1

Compare Source

Bug Fixes

v0.11.0

Compare Source

Features
BREAKING CHANGES

While I endeavor to avoid breaking changes some are necessary to support both better outcomes for implementers and fix issues which are not desirable. This release packs a quite a few, so it's important to take the time to read. While the details on adapting are not comprehensive, they should easy to understand and clarification will be added where it makes sense. Feel free to open a discussion if you're having issues migrating.

  • MAJOR: A majority of the functionality that exists within the metadata package has been completely reworked. The rework has added a number of great validation options for implementers as well as allowing them to more easily manage metadata blobs and the refresh of these blobs in their own domain logic. This will require substantial work for anyone currently using it. I will aim to make a discussion explaining all of it in the coming days.
  • The following fields and backwards compatible elements have been removed; Icon field from the CredentialEntity struct, WebAuthnIcon function from the User interface, RPIcon/RPOrigin/Timeout fields from the Config struct, Transports field from the CredentialCreationResponse (new field has existed in the AuthenticatorAttestationResponse struct for quite some time which matches the spec).
  • The Backup Eligible and Backup State flags within the CredentialFlags struct (field of the Credential struct) are now strictly validated to be consistent with the spec. This breaks implementations which do not strictly adhere to the specification. Several major providers either have or are currently "upgrading" existing WebAuthn credential records to BE and BS passkeys.
  • The default modality values are now empty by default. This allows additional browser flows to be accessible to implementers. This change will change default behavior. Previously the required resident key value was set to false, and the user verification option was set to 'preferred'. Implementers looking for consistent values should customize the Authenticator Selection Criteria during registration.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

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.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@descope descope bot added the renovate label Sep 15, 2024
@shilgapira shilgapira closed this Sep 16, 2024
@shilgapira shilgapira deleted the renovate/github.com-go-webauthn-webauthn-0.x branch September 16, 2024 13:36
@descope
Copy link
Contributor Author

descope bot commented Sep 16, 2024

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update (v0.11.2). You will get a PR once a newer version is released. To ignore this dependency forever, add it to the ignoreDeps array of your Renovate config.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant