Skip to content

Update all non-major dependencies (minor) - #1256

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@owf/cose (source) ^0.4.2 → ^0.7.0 age confidence
@owf/mdoc (source) ^0.8.2 → ^0.9.0 age confidence
@peculiar/x509 2.1.0 → 2.2.0 age confidence
@sd-jwt/core (source) ^0.22.0 → ^0.24.0 age confidence
@sd-jwt/sd-jwt-vc (source) ^0.22.0 → ^0.24.0 age confidence
eslint (source) 10.14.0 → 10.15.0 age confidence
openid-client 6.8.9 → 6.9.0 age confidence
prettier (source) 3.9.10 → 3.10.1 age confidence

Release Notes

openwallet-foundation-labs/identity-common-ts (@​owf/cose)

v0.7.0

Compare Source

Minor Changes
  • 747a242: Support the fully-specified COSE signature algorithms of RFC 9864: SignatureAlgorithm.ESP256 (-9), ESP384 (-51) and ESP512 (-52) from § 2.1, and Ed25519 (-19) and Ed448 (-53) from § 2.2. Sign1.algorithm accepts them. coseKeyToJwkClaim.algorithm and Sign1.jwaAlgorithm convert ESP256, ESP384 and ESP512 to the JWA ES256, ES384 and ES512, and Ed25519 and Ed448 to the JWA names of the same name. jwkToCoseKey.alg('ES256') still returns ES256 (-7), and jwkToCoseKey.alg('Ed25519') returns -19.

    Sign1.sign and Sign1.verifySignature throw CoseInvalidAlgorithmError when the key type or curve of the key does not match the algorithm (RFC 9053 § 2.1 and § 2.2, RFC 9864 § 2.1 and § 2.2). ES256, ES384 and ES512 require an EC2 key on P-256, P-384 or P-521, and EdDSA an OKP key on Ed25519 or Ed448. The fully-specified algorithms require the one curve they are defined for. The alg of the key is not compared, and RSA algorithms are not checked.

    In @owf/mdoc, issuer auth, device auth, reader auth, verifyStatusListToken and verifyIdentifierListToken accept these algorithms. Device auth now verifies through Sign1.verifySignature, so the sign1.verify callback receives the alg of the device signature, and the key check applies to it.

Patch Changes
  • 057107b: Use the registered JWK crv names P-384 and P-521. fromJwk now accepts these values, and .jwk emits them instead of p-384 and p-521.
  • 01b6985: import cbor-x through its pure JS encode/decode entry points, so bundling for Cloudflare Workers and other edge runtimes no longer pulls in the native cbor-extract loader and child_process. This also fixes @owf/token-status-list and @owf/mdoc in those runtimes.
  • Updated dependencies [23f227b]

v0.6.2

Compare Source

Patch Changes

v0.6.1

Compare Source

Patch Changes

v0.6.0

Compare Source

Patch Changes

v0.5.0

Compare Source

Minor Changes
  • b4105be: Drop the CommonJS build from all packages; only ESM is now published. All environments targeted by this library support ESM natively. This removes the dual-package hazard that caused instanceof checks to fail in Metro/Hermes and similar single-module-system runtimes.
Patch Changes
  • b7002dd: Add getIntegrityProtectedX5Chain, which reads the x5chain of a COSE structure from the protected header, or else from the unprotected header when a protected x5t (SHA-256) matches its leaf, as RFC 9360 requires. An unbound unprotected x5chain throws CoseX5ChainNotBoundError.
  • dacb544: Reject a token at its exp instant. verifyStatusListJwtClaims (and so verifyStatus) and CwtPayload.verifyClaims (and so Cwt.verify and StatusListCwtPayload.verifyClaims) accepted a token when the current time was exactly exp plus the skew. RFC 7519 section 4.1.4 says a token MUST NOT be accepted on or after its exp, and RFC 8392 gives exp the same meaning in a CWT. This matches @sd-jwt/core.
  • Updated dependencies [b4105be]
openwallet-foundation-labs/identity-common-ts (@​owf/mdoc)

v0.9.3

Patch Changes
  • 747a242: Support the fully-specified COSE signature algorithms of RFC 9864: SignatureAlgorithm.ESP256 (-9), ESP384 (-51) and ESP512 (-52) from § 2.1, and Ed25519 (-19) and Ed448 (-53) from § 2.2. Sign1.algorithm accepts them. coseKeyToJwkClaim.algorithm and Sign1.jwaAlgorithm convert ESP256, ESP384 and ESP512 to the JWA ES256, ES384 and ES512, and Ed25519 and Ed448 to the JWA names of the same name. jwkToCoseKey.alg('ES256') still returns ES256 (-7), and jwkToCoseKey.alg('Ed25519') returns -19.

    Sign1.sign and Sign1.verifySignature throw CoseInvalidAlgorithmError when the key type or curve of the key does not match the algorithm (RFC 9053 § 2.1 and § 2.2, RFC 9864 § 2.1 and § 2.2). ES256, ES384 and ES512 require an EC2 key on P-256, P-384 or P-521, and EdDSA an OKP key on Ed25519 or Ed448. The fully-specified algorithms require the one curve they are defined for. The alg of the key is not compared, and RSA algorithms are not checked.

    In @owf/mdoc, issuer auth, device auth, reader auth, verifyStatusListToken and verifyIdentifierListToken accept these algorithms. Device auth now verifies through Sign1.verifySignature, so the sign1.verify callback receives the alg of the device signature, and the key check applies to it.

  • Updated dependencies [747a242]

  • Updated dependencies [057107b]

  • Updated dependencies [01b6985]

  • Updated dependencies [23f227b]

v0.9.2

Patch Changes
  • aede3c4: MdocContext.fetch receives a third argument naming what it is retrieving, { type: 'statusList' | 'identifierList' }, so an implementation can cache or time out per resource. An implementation written with a rest parameter needs its parameters named:

    -fetch: (...args) => fetch(...args),
    +fetch: (input, init) => fetch(input, init),
  • bf9b7c8: Accept a status list served as a JWT as a fallback. verifyStatusListToken still requests a CWT first, verifies a JWT (ES256/384/512, signer from x5c) with the same signer, claim and status checks, and returns it as statusListJwt (IssuerAuth.verify verifies it but does not return it); statusListCwt is now optional and JwtNotSupportForStatusListError is deprecated.

  • Updated dependencies [bf9b7c8]

  • Updated dependencies [bf9b7c8]

v0.9.1

Patch Changes

v0.9.0

Minor Changes
  • 5b19cc4: Match the request information of ISO/IEC TS 23220-4 7.2.1, which the second edition of ISO/IEC 18013-5 takes up, holder side (Holder.matchDeviceRequest, Holder.createDeviceResponseForDeviceRequest) and verifier side (matchDeviceRequest, Verifier.verifyDeviceResponse).

    Breaking: a device request is now always matched by use cases. docRequestsAsAlternatives is replaced by useCasesSource and useCases, which every match result carries. Without a deviceRequestInfo, the doc requests are one mandatory use case ('allDocRequests', the default), or one optional use case each with treatAmbiguousMultipleDocRequestsAsAlternatives ('eachDocRequest'). A match succeeds when every mandatory use case and at least one use case are satisfied.

    • use cases: each UseCaseMatch lists the document sets of the use case (documentSets) and those whose doc requests are all satisfied (matchingDocumentSets), for the holder to pick one, with its purposeHints
    • alternative data elements: a requested element is answered by itself or by one of its alternative sets, and the claim lists every option (options), in order of preference. A response only discloses an alternative set the holder chooses with alternatives on the document it creates, never one that discloses an element it leaves out, and a holder is not offered one that would disclose more than two age_over_NN elements in a namespace. The verifier does not report the elements of an alternative set as over-disclosure
    • issuer identifiers: an mdoc only answers a doc request that names issuers when a certificate in its chain has one of them as authority key identifier, reported as issuer on the credential or document match. A verifier matches them against the validated chain, never the x5chain, which is unprotected: Verifier.verifyDeviceResponse passes the chains it validates, and matchDeviceRequest and Verifier.matchDeviceRequest take them as issuerCertificateChains, without which, as with disableCertificateChainValidation, no document satisfies such a doc request. x509.verifyCertificateChain of the context must therefore return only the certificates of the path it validated, not the whole x5chain. The certificates are parsed with @owf/x509
    • attribution: as a response does not say which document answers which doc request, the verifier match works it out as attribution: the doc requests each document answers, and the document set of each use case it is taken to answer. A document may answer every doc request of its docType and of an issuer it accepts, also with elements left out, and one document can answer several. A doc request with uniqueDocSetRequired takes one document only: it fails when the response has more documents than such doc requests can take, or when those documents leave it none that satisfies it, and doc requests and use cases that can each be answered but not together fail the match. This is exact and does not depend on the order of the documents. When a document may also answer a doc request without uniqueDocSetRequired, it is never counted as a second document for one with it. A document that answers no doc request of the sets the use cases are answered with, nor of a use case the response is not taken to answer, is reported as a WARNING, as a holder answers each use case with exactly one document set
    • Holder.createDeviceResponseForDeviceRequest throws an UnsatisfiedDeviceRequestError for a document of an issuer the doc request does not name, a second document for a doc request with uniqueDocSetRequired, a mandatory use case, or every use case, without a document for each doc request of one of its document sets, or a response larger than the smallest maximumResponseSize. Without use cases, which doc requests get a document is not checked, as the iOS DC API presents several doc requests as alternatives
    • docRequestIndex of a document the holder creates takes several doc requests of its docType: the document discloses what all of them request, and counts as the document of each of them
    • IsoMdocDcApi: createRequest takes requestInfo per doc request and deviceRequestInfo, and createResponse takes alternatives per document
  • 448143e: Read and write the request information of ISO/IEC TS 23220-4 7.2.1, which the second edition of ISO/IEC 18013-5 takes up: ItemsRequest.requestInfo (DocRequestInfo: AlternativeDataElementsSets, issuer identifiers, uniqueDocSetRequired, maximumResponseSize) and DeviceRequest.deviceRequestInfo (DeviceRequestInfo: UseCases and their document sets). Unknown keys are ignored and kept, nested ones included, so a request carrying either still re-encodes byte for byte. An invalid value in a known key, or a document set pointing past the doc requests, fails decoding. DeviceRequest.create defaults to version '1.1' when given a deviceRequestInfo, as the second edition of 18013-5 asks.

v0.8.3

Patch Changes
  • 93f6eff: Read a status of null in the MSO as absent. ISO/IEC 18013-5 does not allow null there, but Apple Wallet's developer mDLs send it, which failed with Error decoding Status: Expected map, received null.
  • 6d8e998: Report a status list entry that is not Valid as StatusListEntryNotValidError with its uri, idx and status, so it can be told apart from a status list that fails verification. It extends InvalidRevocationListError. IssuerAuth.verify adds it, or a revoked identifier, to the failed check as a VerificationAssessmentResult.
  • b7002dd: Accept a status list whose x5chain is in the unprotected header when a protected x5t matches its leaf certificate. ISO/IEC 18013-5 § 12.3.6.3 requires the chain in the protected header, but RFC 9360 allows it with that binding. The context of IssuerAuth.verify, IssuerAuth.verifyStatus and verifyStatusListToken now requires crypto to check the x5t.
  • Updated dependencies [b7002dd]
  • Updated dependencies [b4105be]
  • Updated dependencies [dacb544]
PeculiarVentures/x509 (@​peculiar/x509)

v2.2.0

Compare Source

What's Changed

Full Changelog: PeculiarVentures/x509@v2.1.0...v2.2.0

openwallet-foundation-labs/identity-common-ts (@​sd-jwt/core)

v0.24.2

Patch Changes

v0.24.1

Patch Changes
  • 260114a: Verification now rejects an issuer-signed JWT or Key Binding JWT whose header has crit, as RFC 7515 requires for extensions the verifier does not understand, and an SD-JWT VC in which a protected claim (iss, nbf, exp, cnf, vct, vct#integrity or status) arrived in a Disclosure.
  • @​owf/identity-common@0.6.2

v0.24.0

Patch Changes

v0.23.2

Patch Changes

v0.23.1

No changes in this release.

v0.23.0

Minor Changes
  • b4105be: Drop the CommonJS build from all packages; only ESM is now published. All environments targeted by this library support ESM natively. This removes the dual-package hazard that caused instanceof checks to fail in Metro/Hermes and similar single-module-system runtimes.
Patch Changes
openwallet-foundation-labs/identity-common-ts (@​sd-jwt/sd-jwt-vc)

v0.24.2

Patch Changes

v0.24.1

Patch Changes
  • eb3fef1: svg_templates in the type metadata rendering is now optional in the TypeMetadataFormat type. Parsing type metadata without svg_templates or svg_template no longer adds an svg_templates: undefined key.
  • 260114a: Sub-claims of a protected claim can no longer be selectively disclosed, as SD-JWT VC requires. issue rejects a disclosure frame for any sub-claim of iss, nbf, exp, cnf, vct, vct#integrity or status (for example the status_list of status), and verification rejects an SD-JWT VC whose issuer-signed protected claims have a selectively disclosable sub-claim, whether the holder reveals it or not.
  • 260114a: Verification now rejects an issuer-signed JWT or Key Binding JWT whose header has crit, as RFC 7515 requires for extensions the verifier does not understand, and an SD-JWT VC in which a protected claim (iss, nbf, exp, cnf, vct, vct#integrity or status) arrived in a Disclosure.
  • Updated dependencies [260114a]
  • Updated dependencies [13a53dc]

v0.24.0

Minor Changes
  • 1031dd7: Add verifyTypeMetadata to check the claims of an SD-JWT VC against its type metadata: extra claims, missing or undisclosed mandatory claims, and sd violations. verify and safeVerify add the result as typeMetadataVerification when loadTypeMetadataFormat is enabled.
Patch Changes
  • 0957fb1: Fix the mandatory claim checks of verifyTypeMetadata: claim names such as constructor are no longer found on Object.prototype, a mandatory claim under a null path is undisclosed when every element is withheld and missing when the value is not an array, and the vct of type metadata passed by the caller is compared before its extends chain is resolved.
  • 70f7b34: vct#integrity can no longer be made selectively disclosable, as required by SD-JWT VC.
  • Updated dependencies [bf9b7c8]
  • Updated dependencies [bf9b7c8]

v0.23.2

Patch Changes

v0.23.1

Patch Changes
  • 461f847: Resolving type metadata now fails when a fetched document describes a different vct than the one it was fetched for, for the credential's vct and for every extends value. The vctValues of a resolved chain are read from the documents, so before this change whoever hosted a credential's vct URL could serve a document claiming any other type, such as urn:eudi:pid:1, and the credential matched requests for that type.

    A circular extends chain that leads back to the credential's own vct is now detected when it is reached, instead of one fetch later.

  • @​sd-jwt/core@0.23.1

v0.23.0

Minor Changes
  • b4105be: Drop the CommonJS build from all packages; only ESM is now published. All environments targeted by this library support ESM natively. This removes the dual-package hazard that caused instanceof checks to fail in Metro/Hermes and similar single-module-system runtimes.
Patch Changes
  • 47e5ca8: Fix the vct#integrity and extends#integrity checks: the digest is now compared as base64, as defined by W3C Subresource Integrity, instead of hex. When the integrity metadata lists several hashes, only the strongest supported algorithm (sha256, sha384, sha512) is checked and any of its values may match. Integrity metadata without a supported algorithm is rejected.
  • Updated dependencies [b4105be]
  • Updated dependencies [dacb544]
eslint/eslint (eslint)

v10.15.0

Compare Source

Features

  • ec52157 feat: check proto and assignment targets in func-names (#​21521) (Lê Văn Xuân Hoàn)
  • 34a8b1b feat: recognize string and computed keys in accessor-pairs descriptors (#​21519) (Lê Văn Xuân Hoàn)
  • 663c825 feat: handle TS type assertions in no-invalid-this (#​21464) (Valentin)
  • 4941015 feat: check individual specifier importKind in no-shadow (#​21518) (Lê Văn Xuân Hoàn)
  • 17f17cd feat: update error location to head for default-case (#​21469) (Tanuj Kanti)

Bug Fixes

Documentation

  • 16eb1d9 docs: remove Contributor Pool reference (#​21539) (Nicholas C. Zakas)
  • e368730 docs: discourage non-serializable values in rule options (#​21487) (Vitalii Maslianok)
  • 0146008 docs: revamp code path analysis docs (#​21423) (xbinaryx)
  • aeb2267 docs: revise AI acknowledgment options in templates (#​21489) (lumir)
  • e47a477 docs: Update README (GitHub Actions Bot)
  • 11c66ba docs: fix typo in custom rules documentation (#​21472) (Pixel)

Chores

panva/openid-client (openid-client)

v6.9.0

Compare Source

Features
  • add getDecryptedResponses (279212e)
prettier/prettier (prettier)

v3.10.1

Compare Source

diff

GraphQL: Fix empty selection set with comments (#​20504 by @​fisker)
# Input
fragment F on Query {
  # x
}

# Prettier 3.10.0
Error: Comment "x" was not printed. Please report this error!

# Prettier 3.10.1
fragment F on Query {
  # x
}

v3.10.0

Compare Source

diff

🔗 Release Notes


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 06:59 AM, only on Wednesday (* 0-6 * * 3)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies Pull requests that update dependencies label Nov 18, 2026
@renovate
renovate Bot enabled auto-merge (squash) November 18, 2026 05:41
@renovate
renovate Bot requested review from a team, britsta and tnotheis November 18, 2026 08:49

@britsta britsta left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Dependency Security Maintenance pipeline triggered.

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 42ff375 to e9cf97d Compare November 18, 2026 10:05
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from e9cf97d to 5bba974 Compare November 18, 2026 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update dependencies

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant