chore(release): new version - #247
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
4 times, most recently
from
June 30, 2026 08:14
b124642 to
5c2b7b5
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
July 1, 2026 13:24
3395c62 to
62bbbf3
Compare
Signed-off-by: "github-actions[bot]" <"41898282+github-actions[bot]@users.noreply.github.com">
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 1, 2026 13:36
62bbbf3 to
46e8a53
Compare
hacdias
approved these changes
Jul 1, 2026
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
@openid4vc/oauth2@0.5.2
Patch Changes
33adaf0: Align wallet (client) attestation with draft 09 of OAuth 2.0 Attestation-Based Client Authentication.
issclaim (removed in draft 08). Verification still accepts legacy JWTs that includeiss.challengeclaim (renamed fromnoncein draft 06) and no longer includesexp(removed in draft 06). Verification accepts eitherchallengeor the legacynonce. Thenonce/expectedNonceoptions are deprecated aliases forchallenge/expectedChallenge.client_attestation_signing_alg_values_supportedandclient_attestation_pop_signing_alg_values_supported(draft 07), thechallenge_endpointparameter, theattest_jwt_client_auth_dpopauthentication method, and theOAuth-Client-Attestation-Challengeheader (draft 09).verifyClientAttestationPopJwtaccepts anexpectedAudienceoption so a resource server can verify a PoP JWT bound to its own identifier (draft 09).@openid4vc/openid4vci@0.5.2
Patch Changes
78cdbca: Bring key attestations in line with the OpenID4VCI 1.0/1.1 key attestation format.
key-attestation+jwtas thetypwhen creating a key attestation (previously the pre-finalkeyattestation+jwt). Verification still accepts the legacy value.trust_chainandkid; the spec requireskidto be present whentrust_chainis used for signature verification (fixed for both the key attestation and thejwtproof type headers).attested_keys(and, when present,key_storage/user_authentication) to be non-empty arrays.nonceclaim optional at the schema level; it is only required when the Credential Issuer has a Nonce Endpoint, which is enforced viaexpectedNonceduring verification.fe01c0d: Fix credential response check to match spec definition
Updated dependencies [33adaf0]
@openid4vc/openid4vp@0.5.2
Patch Changes
@openid4vc/utils@0.5.2