fix(deps): Update did-vc-libraries (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@aviarytech/did-peer	^0.0.22 → ^1.0.0
@digitalcredentials/ed25519-signature-2020	^4.0.0 → ^7.0.0
@digitalcredentials/ed25519-verification-key-2020	^4.0.0 → ^5.0.0
@digitalcredentials/jsonld	^6.0.0 → ^9.0.0
@digitalcredentials/jsonld-signatures	^10.0.0 → ^12.0.0
@digitalcredentials/vc	^7.0.0 → ^10.0.0
did-resolver	^4.1.0 → ^5.0.0
ethr-did-resolver	^11.0.2 → ^13.0.0
jsonld	^6.0.0 → ^9.0.0

---

Release Notes

aviarytech/did-peer (@​aviarytech/did-peer)

v1.1.2

Compare Source

Bug Fixes

• Consolidate utility functions and improve code clarity (3a20c92)

v1.1.1

Compare Source

Bug Fixes

• Restore multicodec prefix handling in createNumAlgo4 function (dcb3f4c)
• Simplify JSON encoding in createNumAlgo4 function (b771697)

v1.1.0

Compare Source

Features

• Allow additional custom properties on service descriptors (5463353)

1.0.2 (2025-07-28)

Bug Fixes

• Update semantic-release configuration for npm publishing (9cb0a9c)

1.0.1 (2025-07-28)

Bug Fixes

• Remove debug step for NPM_TOKEN in npm-publish workflow (b5f2834)

v1.0.2

Compare Source

Bug Fixes

• Update semantic-release configuration for npm publishing (9cb0a9c)

v1.0.1

Compare Source

Bug Fixes

• Remove debug step for NPM_TOKEN in npm-publish workflow (b5f2834)

v1.0.0

Compare Source

Bug Fixes

• Add @​base to base context (127a675)
• Add @​base to context when services are used (907574e)
• Address PR feedback (59773d8)
• did-peer-2 allows for multiple service blocks (034a3f7)
• key-ids should match spec (445c1be)
• Remove unused attributes (8dd2b3a)
• support for multiple service blocks (17bc44a)
• switch to multikey for Numalgo 2+ (1b81151)

digitalcredentials/ed25519-signature-2020 (@​digitalcredentials/ed25519-signature-2020)

v7.0.0

Compare Source

Changed

• BREAKING: Removes support for cjs
• Updates from latest DigitalBazaar upstream

v6.0.0

Compare Source

Changed

• BREAKING: The dependency @digitalcredentials/jsonld-signatures@12.0.0 now requires
  expo-crypto for React Native sha256 digest hashing, instead of
  @sphereon/isomorphic-webcrypto@2.5.0-unstable.0.
  • IMPORTANT: This means that IF you're using this library inside a React Native project, you MUST include expo-crypto
    in your project's dependencies.

v5.0.0

Compare Source

Changed

• BREAKING: Update to @digitalcredentials/jsonld-signatures v11.0.0 (latest Sphereon webcrypto fork, latest DCC forks of jsonld and http-client).
• BREAKING: Reverts cache clearing behavior of v10.0.0.

digitalcredentials/ed25519-verification-key-2020 (@​digitalcredentials/ed25519-verification-key-2020)

v5.0.0

Compare Source

Changed

• Update to @digitalcredentials/keypair@3.0.0 and
  @digitalcredentials/ssi@5.2.0 libraries.

digitalcredentials/jsonld.js (@​digitalcredentials/jsonld)

v9.0.0

Compare Source

Changed

• BREAKING: Re-fork as @digitalcredentials/jsonld (to fix upstream http-client export error).
• Use @digitalcredentials/http-client@5.0.0 fork.

digitalcredentials/jsonld-signatures (@​digitalcredentials/jsonld-signatures)

v12.0.1

Compare Source

Fixed

• Fix expo-crypto browser export.

v12.0.0

Compare Source

Changed

• BREAKING: Now uses expo-crypto for React Native sha256 digest hashing, instead of
  @sphereon/isomorphic-webcrypto@2.5.0-unstable.0.
  • IMPORTANT: This means that IF you're using this library inside a React Native project, you MUST include expo-crypto
    in your project's dependencies.

v11.0.0

Compare Source

Changed

• BREAKING: Now uses DCC forks of jsonld and http-client.

digitalcredentials/vc (@​digitalcredentials/vc)

v10.0.2

Compare Source

Changed

• Fix createPresentation throwing expiration error when verify: false.

v10.0.1

Compare Source

Changed

• Add a parameter to createPresentation to allow VC verification to be optional.
  Addresses issue #​32. Does not change current default behavior.

v10.0.0

Compare Source

Changed

• BREAKING: Removes CJS build

Fixed

• move status check before expiry check because expiry check throws error that had prevented the status check from running
• attach the credential to the verification result for each credential submitted as part of a VP verification

v9.0.1

Compare Source

Fixed

• add signature checks to the log before running other verification checks whose errors might prevent that logging

v9.0.0

Compare Source

Changed

• BREAKING: The dependency @digitalcredentials/jsonld-signatures@12.0.0 (via @digitalcredentials/ed25519-signature-2020)
  now requires expo-crypto for React Native sha256 digest hashing, instead of
  @sphereon/isomorphic-webcrypto@2.5.0-unstable.0.
  • IMPORTANT: This means that IF you're using this library inside a React Native project, you MUST include expo-crypto
    in your project's dependencies.

v8.0.1

Compare Source

Fixed

• Fix stray Error object in CredentialIssuancePurpose.

v8.0.0

Compare Source

Added

• Add support for VC 2.0 Verifiable Credentials issuance and verification.
• Add support for VC 2.0 Verifiable Presentations issuance and verification.
• Add support for VC 2.0 validFrom and validUntil.
• Add Test vectors for VC 2.0 VCs & VPs.
• Allow credentialStatus arrays in credential status check.
• Add derive() API for deriving new verifiable credentials from
  existing ones, for the purpose of selective disclosure or
  unlinkable presentation.
• Add optional param now to verifyCredential(), createPresentation(),
  verify(), and issue().

Changed

• BREAKING: Switch dependencies to:
  • @digitalcredentials/jsonld
  • @digitalcredentials/jsonld-signatures
  • @digitalcredentials/http-client
• BREAKING: Default issuance now uses VC 2.0 context.
• BREAKING: DateTime validator is now an xml schema DateTime validator.
• Change engines.node to >=18 to support newer keys & suites.
• Update dependencies.
  • BREAKING: Remove support for expansionMap. (Removed in dependencies.)
• BREAKING: Use jsonld-signatures@11 and jsonld@8 to get new safe
  mode (and on by default when using canonize) feature.
• BREAKING: Check if credential has expired when expirationDate property
  exists.
• BREAKING: Convert to module (ESM).
• BREAKING: Require Node.js >=14.
• Update dependencies.
  • BREAKING: did-veres-one@15.0.0 used in tests.
• Lint module.

Fixed

• Ensure that issuanceDate is only checked on verification,
  not issuance.
• Fix bug with option overrides for verifying presentations.

Removed

• BREAKING: Remove ODRL and VC examples contexts from ./lib/contexts/ and
  from the default document loader. The contexts are now available in
  @digitalbazaar/odrl-context
  and
  @digitalbazaar/credentials-examples-context.

decentralized-identity/did-resolver (did-resolver)

v5.0.1

Compare Source

Bug Fixes

• types: refine @context and verification method types for improved extensibility (#​156) (2ad4c48)

v5.0.0

Compare Source

• Publishing maintenance (#​155) (86f81fe), closes #​155

BREAKING CHANGES

• the package.json exports is changing and this usually counts as a breaking change. Raising the compile target from ES2018 to ES2020 changes the runtime syntax, also counts as breaking.

decentralized-identity/ethr-did-resolver (ethr-did-resolver)

v13.0.0

Compare Source

Bug Fixes

• build: update typescript to 6.0.3 (201a50c)

BREAKING CHANGES

• build: PR #​236 updated the exports property to match new ESM/CJS project layout

12.0.1 (2026-05-18)

Bug Fixes

• build: split ESM/CJS build steps (#​236) (8eeff0e), closes #​211

v12.0.1

Compare Source

Bug Fixes

• build: update typescript to 6.0.3 (201a50c)

BREAKING CHANGES

• build: PR #​236 updated the exports property to match new ESM/CJS project layout

12.0.1 (2026-05-18)

Bug Fixes

• build: split ESM/CJS build steps (#​236) (8eeff0e), closes #​211

v12.0.0

Compare Source

Bug Fixes

• build: update typescript to 6.0.3 (201a50c)

BREAKING CHANGES

• build: PR #​236 updated the exports property to match new ESM/CJS project layout

12.0.1 (2026-05-18)

Bug Fixes

• build: split ESM/CJS build steps (#​236) (8eeff0e), closes #​211

v11.1.3

Compare Source

Features

• support additional key types in the reference resolver implementation (#​229) (1463f93)

BREAKING CHANGES

• attrTypes and delegateTypes are no longer exported as they mapped to the deprecated VM names.

• feat: upgrade key->VM mappings to modern variants an add extra key types

• Ed25519 => Ed25519VerificationKey2020 instead of 2018

• X25519 => X25519KeyAgreementKey2020
  instead of 2019

• The #controllerKey is now resolved using publicKeyJwk instead of publicKeyHex

• added Multikey & BLS key support

• the resolved DID documents now display the modern, spec compliant, Verification Methods for several key types, ignoring the encoding hint, effectively changing the output. Ed25519/X25519 VM methods now map to their 2020 definitions.

• chore: define extra multicodec prefixes for known key types

• refactor: avoid using Buffer in conversions

• feat: output secp256k1 keys as JWK

• Update resolver to use publicKeyJwk for secp256k1 keys, ignoring the encoding hint.

• refactor: remove DEFAULT_REGISTRY_ADDRESS and require explicit registry address for networks

• Remove REGISTRY export from index. The default registry address is misleading as it refers to an older build of the registry contract that is no longer deployed on most networks. The resolver should throw if there is no registry configured.

• refactor: replace enums with const objects and types for VMTypes, eventNames, and Errors

• feat: support multiple public key property types in context generation

• refactor: always emit publicKey data for known key types and remove keyDataSet checks

• refactor: remove unnecessary type assertion for publicKeyJwk in controller key generation

• refactor: centralize deployment matching logic and update registry param docs

• refactor: remove unused RSA & publicKeyPem handling

• RSA keys no longer directly handled. There is no history of usage, but still counts as breaking.

• The encoding hint from DIDAttributeChanged is only used when the key type is unknown. If none is specified, publicKeyHex is used.

• refactor: remove Bls12381G1/G2 key type handling and tests in favor of Multikey

11.1.3 (2026-05-07)

Bug Fixes

• ci: fix typo in release rc file (#​233) (a7e9bc1)
• ci: harden ci workflows (#​231) (94a6ea3)
• ci: pin pnpm to exact version in workflows (#​232) (60d865f)

11.1.2 (2026-05-04)

Bug Fixes

• deps: Update dependency did-resolver to v5.0.1 (87a50ea)

11.1.1 (2026-05-04)

Bug Fixes

• deps: Update dependency did-resolver to v5 (b682d34)

v11.1.2

Compare Source

Features

• support additional key types in the reference resolver implementation (#​229) (1463f93)

BREAKING CHANGES

• attrTypes and delegateTypes are no longer exported as they mapped to the deprecated VM names.

• feat: upgrade key->VM mappings to modern variants an add extra key types

• Ed25519 => Ed25519VerificationKey2020 instead of 2018

• X25519 => X25519KeyAgreementKey2020
  instead of 2019

• The #controllerKey is now resolved using publicKeyJwk instead of publicKeyHex

• added Multikey & BLS key support

• the resolved DID documents now display the modern, spec compliant, Verification Methods for several key types, ignoring the encoding hint, effectively changing the output. Ed25519/X25519 VM methods now map to their 2020 definitions.

• chore: define extra multicodec prefixes for known key types

• refactor: avoid using Buffer in conversions

• feat: output secp256k1 keys as JWK

• Update resolver to use publicKeyJwk for secp256k1 keys, ignoring the encoding hint.

• refactor: remove DEFAULT_REGISTRY_ADDRESS and require explicit registry address for networks

• Remove REGISTRY export from index. The default registry address is misleading as it refers to an older build of the registry contract that is no longer deployed on most networks. The resolver should throw if there is no registry configured.

• refactor: replace enums with const objects and types for VMTypes, eventNames, and Errors

• feat: support multiple public key property types in context generation

• refactor: always emit publicKey data for known key types and remove keyDataSet checks

• refactor: remove unnecessary type assertion for publicKeyJwk in controller key generation

• refactor: centralize deployment matching logic and update registry param docs

• refactor: remove unused RSA & publicKeyPem handling

• RSA keys no longer directly handled. There is no history of usage, but still counts as breaking.

• The encoding hint from DIDAttributeChanged is only used when the key type is unknown. If none is specified, publicKeyHex is used.

• refactor: remove Bls12381G1/G2 key type handling and tests in favor of Multikey

11.1.3 (2026-05-07)

Bug Fixes

• ci: fix typo in release rc file (#​233) (a7e9bc1)
• ci: harden ci workflows (#​231) (94a6ea3)
• ci: pin pnpm to exact version in workflows (#​232) (60d865f)

11.1.2 (2026-05-04)

Bug Fixes

• deps: Update dependency did-resolver to v5.0.1 (87a50ea)

11.1.1 (2026-05-04)

Bug Fixes

• deps: Update dependency did-resolver to v5 (b682d34)

v11.1.1

Compare Source

Features

• support additional key types in the reference resolver implementation (#​229) (1463f93)

BREAKING CHANGES

• attrTypes and delegateTypes are no longer exported as they mapped to the deprecated VM names.

• feat: upgrade key->VM mappings to modern variants an add extra key types

• Ed25519 => Ed25519VerificationKey2020 instead of 2018

• X25519 => X25519KeyAgreementKey2020
  instead of 2019

• The #controllerKey is now resolved using publicKeyJwk instead of publicKeyHex

• added Multikey & BLS key support

• the resolved DID documents now display the modern, spec compliant, Verification Methods for several key types, ignoring the encoding hint, effectively changing the output. Ed25519/X25519 VM methods now map to their 2020 definitions.

• chore: define extra multicodec prefixes for known key types

• refactor: avoid using Buffer in conversions

• feat: output secp256k1 keys as JWK

• Update resolver to use publicKeyJwk for secp256k1 keys, ignoring the encoding hint.

• refactor: remove DEFAULT_REGISTRY_ADDRESS and require explicit registry address for networks

• Remove REGISTRY export from index. The default registry address is misleading as it refers to an older build of the registry contract that is no longer deployed on most networks. The resolver should throw if there is no registry configured.

• refactor: replace enums with const objects and types for VMTypes, eventNames, and Errors

• feat: support multiple public key property types in context generation

• refactor: always emit publicKey data for known key types and remove keyDataSet checks

• refactor: remove unnecessary type assertion for publicKeyJwk in controller key generation

• refactor: centralize deployment matching logic and update registry param docs

• refactor: remove unused RSA & publicKeyPem handling

• RSA keys no longer directly handled. There is no history of usage, but still counts as breaking.

• The encoding hint from DIDAttributeChanged is only used when the key type is unknown. If none is specified, publicKeyHex is used.

• refactor: remove Bls12381G1/G2 key type handling and tests in favor of Multikey

11.1.3 (2026-05-07)

Bug Fixes

• ci: fix typo in release rc file (#​233) (a7e9bc1)
• ci: harden ci workflows (#​231) (94a6ea3)
• ci: pin pnpm to exact version in workflows (#​232) (60d865f)

11.1.2 (2026-05-04)

Bug Fixes

• deps: Update dependency did-resolver to v5.0.1 (87a50ea)

11.1.1 (2026-05-04)

Bug Fixes

• deps: Update dependency did-resolver to v5 (b682d34)

v11.1.0

Compare Source

Features

• support additional key types in the reference resolver implementation (#​229) (1463f93)

BREAKING CHANGES

• attrTypes and delegateTypes are no longer exported as they mapped to the deprecated VM names.

• feat: upgrade key->VM mappings to modern variants an add extra key types

• Ed25519 => Ed25519VerificationKey2020 instead of 2018

• X25519 => X25519KeyAgreementKey2020
  instead of 2019

• The #controllerKey is now resolved using publicKeyJwk instead of publicKeyHex

• added Multikey & BLS key support

• the resolved DID documents now display the modern, spec compliant, Verification Methods for several key types, ignoring the encoding hint, effectively changing the output. Ed25519/X25519 VM methods now map to their 2020 definitions.

• chore: define extra multicodec prefixes for known key types

• refactor: avoid using Buffer in conversions

• feat: output secp256k1 keys as JWK

• Update resolver to use publicKeyJwk for secp256k1 keys, ignoring the encoding hint.

• refactor: remove DEFAULT_REGISTRY_ADDRESS and require explicit registry address for networks

• Remove REGISTRY export from index. The default registry address is misleading as it refers to an older build of the registry contract that is no longer deployed on most networks. The resolver should throw if there is no registry configured.

• refactor: replace enums with const objects and types for VMTypes, eventNames, and Errors

• feat: support multiple public key property types in context generation

• refactor: always emit publicKey data for known key types and remove keyDataSet checks

• refactor: remove unnecessary type assertion for publicKeyJwk in controller key generation

• refactor: centralize deployment matching logic and update registry param docs

• refactor: remove unused RSA & publicKeyPem handling

• RSA keys no longer directly handled. There is no history of usage, but still counts as breaking.

• The encoding hint from DIDAttributeChanged is only used when the key type is unknown. If none is specified, publicKeyHex is used.

• refactor: remove Bls12381G1/G2 key type handling and tests in favor of Multikey

11.1.3 (2026-05-07)

Bug Fixes

• ci: fix typo in release rc file (#​233) (a7e9bc1)
• ci: harden ci workflows (#​231) (94a6ea3)
• ci: pin pnpm to exact version in workflows (#​232) (60d865f)

11.1.2 (2026-05-04)

Bug Fixes

• deps: Update dependency did-resolver to v5.0.1 (87a50ea)

11.1.1 (2026-05-04)

Bug Fixes

• deps: Update dependency did-resolver to v5 (b682d34)

v11.0.5

Compare Source

Features

• error-handling: Intentionally fail resolution if the RPC endpoint is not serving historical data (#​214) (ae6beeb)

11.0.5 (2025-08-10)

Bug Fixes

• deps: update dependency ethers to v6.15.0 (9f3ad3c)

11.0.4 (2025-06-13)

Bug Fixes

• deps: update dependency ethers to v6.14.4 (#​210) (b3574a2)

11.0.3 (2025-01-06)

Bug Fixes

• deps: update dependency ethers to v6.13.5 (36f50af)

11.0.2 (2024-10-12)

Bug Fixes

• deps: update dependency ethers to v6.13.4 (f940b8e)

11.0.1 (2024-10-01)

Bug Fixes

• deps: update dependency ethers to v6.13.3 (840f6d4)

v11.0.4

Compare Source

Features

• error-handling: Intentionally fail resolution if the RPC endpoint is not serving historical data (#​214) (ae6beeb)

11.0.5 (2025-08-10)

Bug Fixes

• deps: update dependency ethers to v6.15.0 (9f3ad3c)

11.0.4 (2025-06-13)

Bug Fixes

• deps: update dependency ethers to v6.14.4 (#​210) (b3574a2)

11.0.3 (2025-01-06)

Bug Fixes

• deps: update dependency ethers to v6.13.5 (36f50af)

11.0.2 (2024-10-12)

Bug Fixes

• deps: update dependency ethers to v6.13.4 (f940b8e)

11.0.1 (2024-10-01)

Bug Fixes

• deps: update dependency ethers to v6.13.3 (840f6d4)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "before 5am"
• 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]

Branch automerge failure

This PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.

---

• Branch has one or more failed status checks