Repository navigation
Update all non-major dependencies (minor) - #1256
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
britsta
reviewed
Nov 18, 2026
britsta
left a comment
Contributor
There was a problem hiding this comment.
Dependency Security Maintenance pipeline triggered.
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 18, 2026 10:05
42ff375 to
e9cf97d
Compare
renovate
Bot
force-pushed
the
renovate/all-minor-patch
branch
from
November 18, 2026 11:56
e9cf97d to
5bba974
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:
^0.4.2→^0.7.0^0.8.2→^0.9.02.1.0→2.2.0^0.22.0→^0.24.0^0.22.0→^0.24.010.14.0→10.15.06.8.9→6.9.03.9.10→3.10.1Release Notes
openwallet-foundation-labs/identity-common-ts (@owf/cose)
v0.7.0Compare Source
Minor Changes
747a242: Support the fully-specified COSE signature algorithms of RFC 9864:SignatureAlgorithm.ESP256(-9),ESP384(-51) andESP512(-52) from § 2.1, andEd25519(-19) andEd448(-53) from § 2.2.Sign1.algorithmaccepts them.coseKeyToJwkClaim.algorithmandSign1.jwaAlgorithmconvert ESP256, ESP384 and ESP512 to the JWAES256,ES384andES512, andEd25519and Ed448 to the JWA names of the same name.jwkToCoseKey.alg('ES256')still returnsES256(-7), andjwkToCoseKey.alg('Ed25519')returns -19.Sign1.signandSign1.verifySignaturethrowCoseInvalidAlgorithmErrorwhen 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 onEd25519or Ed448. The fully-specified algorithms require the one curve they are defined for. Thealgof the key is not compared, and RSA algorithms are not checked.In
@owf/mdoc, issuer auth, device auth, reader auth,verifyStatusListTokenandverifyIdentifierListTokenaccept these algorithms. Device auth now verifies throughSign1.verifySignature, so thesign1.verifycallback receives thealgof the device signature, and the key check applies to it.Patch Changes
057107b: Use the registered JWKcrvnamesP-384andP-521.fromJwknow accepts these values, and.jwkemits them instead ofp-384andp-521.01b6985: importcbor-xthrough its pure JSencode/decodeentry points, so bundling for Cloudflare Workers and other edge runtimes no longer pulls in the nativecbor-extractloader andchild_process. This also fixes@owf/token-status-listand@owf/mdocin those runtimes.23f227b]v0.6.2Compare Source
Patch Changes
v0.6.1Compare Source
Patch Changes
bf9b7c8]v0.6.0Compare Source
Patch Changes
v0.5.0Compare 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 causedinstanceofchecks to fail in Metro/Hermes and similar single-module-system runtimes.Patch Changes
b7002dd: AddgetIntegrityProtectedX5Chain, which reads thex5chainof a COSE structure from the protected header, or else from the unprotected header when a protectedx5t(SHA-256) matches its leaf, as RFC 9360 requires. An unbound unprotectedx5chainthrowsCoseX5ChainNotBoundError.dacb544: Reject a token at itsexpinstant.verifyStatusListJwtClaims(and soverifyStatus) andCwtPayload.verifyClaims(and soCwt.verifyandStatusListCwtPayload.verifyClaims) accepted a token when the current time was exactlyexpplus the skew. RFC 7519 section 4.1.4 says a token MUST NOT be accepted on or after itsexp, and RFC 8392 givesexpthe same meaning in a CWT. This matches@sd-jwt/core.b4105be]openwallet-foundation-labs/identity-common-ts (@owf/mdoc)
v0.9.3Patch Changes
747a242: Support the fully-specified COSE signature algorithms of RFC 9864:SignatureAlgorithm.ESP256(-9),ESP384(-51) andESP512(-52) from § 2.1, andEd25519(-19) andEd448(-53) from § 2.2.Sign1.algorithmaccepts them.coseKeyToJwkClaim.algorithmandSign1.jwaAlgorithmconvert ESP256, ESP384 and ESP512 to the JWAES256,ES384andES512, andEd25519and Ed448 to the JWA names of the same name.jwkToCoseKey.alg('ES256')still returnsES256(-7), andjwkToCoseKey.alg('Ed25519')returns -19.Sign1.signandSign1.verifySignaturethrowCoseInvalidAlgorithmErrorwhen 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 onEd25519or Ed448. The fully-specified algorithms require the one curve they are defined for. Thealgof the key is not compared, and RSA algorithms are not checked.In
@owf/mdoc, issuer auth, device auth, reader auth,verifyStatusListTokenandverifyIdentifierListTokenaccept these algorithms. Device auth now verifies throughSign1.verifySignature, so thesign1.verifycallback receives thealgof the device signature, and the key check applies to it.Updated dependencies [
747a242]Updated dependencies [
057107b]Updated dependencies [
01b6985]Updated dependencies [
23f227b]v0.9.2Patch Changes
aede3c4:MdocContext.fetchreceives 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:bf9b7c8: Accept a status list served as a JWT as a fallback.verifyStatusListTokenstill requests a CWT first, verifies a JWT (ES256/384/512, signer fromx5c) with the same signer, claim and status checks, and returns it asstatusListJwt(IssuerAuth.verifyverifies it but does not return it);statusListCwtis now optional andJwtNotSupportForStatusListErroris deprecated.Updated dependencies [
bf9b7c8]Updated dependencies [
bf9b7c8]v0.9.1Patch Changes
v0.9.0Minor 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.
docRequestsAsAlternativesis replaced byuseCasesSourceanduseCases, which every match result carries. Without adeviceRequestInfo, the doc requests are one mandatory use case ('allDocRequests', the default), or one optional use case each withtreatAmbiguousMultipleDocRequestsAsAlternatives('eachDocRequest'). A match succeeds when every mandatory use case and at least one use case are satisfied.UseCaseMatchlists the document sets of the use case (documentSets) and those whose doc requests are all satisfied (matchingDocumentSets), for the holder to pick one, with itspurposeHintsoptions), in order of preference. A response only discloses an alternative set the holder chooses withalternativeson 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 twoage_over_NNelements in a namespace. The verifier does not report the elements of an alternative set as over-disclosureissueron the credential or document match. A verifier matches them against the validated chain, never the x5chain, which is unprotected:Verifier.verifyDeviceResponsepasses the chains it validates, andmatchDeviceRequestandVerifier.matchDeviceRequesttake them asissuerCertificateChains, without which, as withdisableCertificateChainValidation, no document satisfies such a doc request.x509.verifyCertificateChainof the context must therefore return only the certificates of the path it validated, not the whole x5chain. The certificates are parsed with@owf/x509attribution: 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 withuniqueDocSetRequiredtakes 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 withoutuniqueDocSetRequired, 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 aWARNING, as a holder answers each use case with exactly one document setHolder.createDeviceResponseForDeviceRequestthrows anUnsatisfiedDeviceRequestErrorfor a document of an issuer the doc request does not name, a second document for a doc request withuniqueDocSetRequired, 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 smallestmaximumResponseSize. Without use cases, which doc requests get a document is not checked, as the iOS DC API presents several doc requests as alternativesdocRequestIndexof 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 themIsoMdocDcApi:createRequesttakesrequestInfoper doc request anddeviceRequestInfo, andcreateResponsetakesalternativesper document448143e: 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) andDeviceRequest.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.createdefaults to version'1.1'when given adeviceRequestInfo, as the second edition of 18013-5 asks.v0.8.3Patch Changes
93f6eff: Read astatusofnullin the MSO as absent. ISO/IEC 18013-5 does not allownullthere, but Apple Wallet's developer mDLs send it, which failed withError decoding Status: Expected map, received null.6d8e998: Report a status list entry that is not Valid asStatusListEntryNotValidErrorwith itsuri,idxandstatus, so it can be told apart from a status list that fails verification. It extendsInvalidRevocationListError.IssuerAuth.verifyadds it, or a revoked identifier, to the failed check as aVerificationAssessmentResult.b7002dd: Accept a status list whosex5chainis in the unprotected header when a protectedx5tmatches 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 ofIssuerAuth.verify,IssuerAuth.verifyStatusandverifyStatusListTokennow requirescryptoto check thex5t.b7002dd]b4105be]dacb544]PeculiarVentures/x509 (@peculiar/x509)
v2.2.0Compare 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.2Patch Changes
23f227b]v0.24.1Patch Changes
260114a: Verification now rejects an issuer-signed JWT or Key Binding JWT whose header hascrit, 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#integrityorstatus) arrived in a Disclosure.v0.24.0Patch Changes
bf9b7c8]v0.23.2Patch Changes
v0.23.1No changes in this release.
v0.23.0Minor 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 causedinstanceofchecks to fail in Metro/Hermes and similar single-module-system runtimes.Patch Changes
b4105be]openwallet-foundation-labs/identity-common-ts (@sd-jwt/sd-jwt-vc)
v0.24.2Patch Changes
23f227b]v0.24.1Patch Changes
eb3fef1:svg_templatesin the type metadata rendering is now optional in theTypeMetadataFormattype. Parsing type metadata withoutsvg_templatesorsvg_templateno longer adds ansvg_templates: undefinedkey.260114a: Sub-claims of a protected claim can no longer be selectively disclosed, as SD-JWT VC requires.issuerejects a disclosure frame for any sub-claim ofiss,nbf,exp,cnf,vct,vct#integrityorstatus(for example thestatus_listofstatus), 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 hascrit, 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#integrityorstatus) arrived in a Disclosure.260114a]13a53dc]v0.24.0Minor Changes
1031dd7: AddverifyTypeMetadatato check the claims of an SD-JWT VC against its type metadata: extra claims, missing or undisclosed mandatory claims, andsdviolations.verifyandsafeVerifyadd the result astypeMetadataVerificationwhenloadTypeMetadataFormatis enabled.Patch Changes
0957fb1: Fix the mandatory claim checks ofverifyTypeMetadata: claim names such asconstructorare no longer found onObject.prototype, a mandatory claim under anullpath 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 itsextendschain is resolved.70f7b34:vct#integritycan no longer be made selectively disclosable, as required by SD-JWT VC.bf9b7c8]bf9b7c8]v0.23.2Patch Changes
v0.23.1Patch Changes
461f847: Resolving type metadata now fails when a fetched document describes a differentvctthan the one it was fetched for, for the credential'svctand for everyextendsvalue. ThevctValuesof a resolved chain are read from the documents, so before this change whoever hosted a credential'svctURL could serve a document claiming any other type, such asurn:eudi:pid:1, and the credential matched requests for that type.A circular
extendschain that leads back to the credential's ownvctis now detected when it is reached, instead of one fetch later.@sd-jwt/core@0.23.1
v0.23.0Minor 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 causedinstanceofchecks to fail in Metro/Hermes and similar single-module-system runtimes.Patch Changes
47e5ca8: Fix thevct#integrityandextends#integritychecks: 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.b4105be]dacb544]eslint/eslint (eslint)
v10.15.0Compare Source
Features
ec52157feat: check proto and assignment targets infunc-names(#21521) (Lê Văn Xuân Hoàn)34a8b1bfeat: recognize string and computed keys inaccessor-pairsdescriptors (#21519) (Lê Văn Xuân Hoàn)663c825feat: handle TS type assertions inno-invalid-this(#21464) (Valentin)4941015feat: check individual specifier importKind inno-shadow(#21518) (Lê Văn Xuân Hoàn)17f17cdfeat: update error location to head fordefault-case(#21469) (Tanuj Kanti)Bug Fixes
23ac66cfix: update dependency @eslint/config-array to ^0.23.6 (#21550) (renovate[bot])df71e34fix: skipno-prototype-builtinssuggestion when object issuper(#21535) (KooYS)899065efix: preserve inlinetypemodifier inno-useless-renameautofix (#21527) (sethamus)af4c3a9fix: preserve TypeScript type parameters inprefer-arrow-callback(#21507) (Lê Văn Xuân Hoàn)b11bcb3fix: preserve necessary parens inno-unneeded-ternaryautofix (#21495) (Lê Văn Xuân Hoàn)7c7292efix: requireminimatch@11.0.1or higher to avoid CVE-2026-118764 (#21492) (nikolawork)Documentation
16eb1d9docs: remove Contributor Pool reference (#21539) (Nicholas C. Zakas)e368730docs: discourage non-serializable values in rule options (#21487) (Vitalii Maslianok)0146008docs: revamp code path analysis docs (#21423) (xbinaryx)aeb2267docs: revise AI acknowledgment options in templates (#21489) (lumir)e47a477docs: Update README (GitHub Actions Bot)11c66badocs: fix typo in custom rules documentation (#21472) (Pixel)Chores
480afadchore: update github/codeql-action action to v4.39.3 (#21533) (renovate[bot])fc3a99bchore: update ecosystem plugins (#21511) (ESLint Bot)8fe3ab9chore: replacegotwith Node.js nativefetch(#21505) (lumir)bdd4b1dci: bump pnpm/action-setup from 6.1.0 to 6.1.1 (#21499) (dependabot[bot])36db635ci: bump github/codeql-action from 4.39.1 to 4.39.2 (#21500) (dependabot[bot])19211b3chore: replacefs-teardownwith Node.js native APIs (#21488) (lumir)bbede5echore: enforcerequire-meta-docs-recommended(#21496) (lumir)896b8adchore: update ecosystem plugins (#21478) (ESLint Bot)35801a2ci: re-enableeslint-plugin-unicornecosystem test (#21470) (Francesco Trotta)panva/openid-client (openid-client)
v6.9.0Compare Source
Features
prettier/prettier (prettier)
v3.10.1Compare Source
diff
GraphQL: Fix empty selection set with comments (#20504 by @fisker)
v3.10.0Compare Source
diff
🔗 Release Notes
Configuration
📅 Schedule: (UTC)
* 0-6 * * 3)🚦 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.
This PR was generated by Mend Renovate. View the repository job log.