fix(deps): Update did-vc-libraries (major)#1463
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
Contributor
Author
Branch automerge failureThis PR was configured for branch automerge. However, this is not possible, so it has been raised as a PR instead.
|
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
August 31, 2025 12:51
78bd3c3 to
9baad96
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
4 times, most recently
from
September 13, 2025 08:54
cfcd791 to
03acafa
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
September 23, 2025 19:02
03acafa to
606489a
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
October 3, 2025 01:54
606489a to
9be3ccc
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
2 times, most recently
from
October 16, 2025 02:05
b0cc84e to
9896996
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
November 10, 2025 17:39
9896996 to
c9a5217
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
November 20, 2025 01:39
c9a5217 to
106b90d
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
December 23, 2025 14:19
106b90d to
72e25e4
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
December 31, 2025 17:56
72e25e4 to
77100e0
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
6 times, most recently
from
January 19, 2026 18:56
bc898ce to
e96869a
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
2 times, most recently
from
January 24, 2026 11:29
b8d6adc to
62ab678
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
February 2, 2026 19:31
62ab678 to
44d1218
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
3 times, most recently
from
February 11, 2026 13:09
529364e to
29436ae
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
March 5, 2026 20:03
29436ae to
d841e0e
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
March 13, 2026 15:16
d841e0e to
4dbc7a3
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
April 1, 2026 16:43
4dbc7a3 to
228d7da
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
3 times, most recently
from
May 4, 2026 19:00
fa1d409 to
a76c4ba
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
May 8, 2026 13:51
a76c4ba to
b814b72
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
2 times, most recently
from
May 18, 2026 18:10
cdac4f4 to
8df58ba
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
June 11, 2026 18:56
8df58ba to
d3bebb5
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
June 22, 2026 20:09
d3bebb5 to
0ae5d79
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
July 1, 2026 12:55
0ae5d79 to
f8ab486
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
July 12, 2026 12:21
f8ab486 to
4eb42c4
Compare
renovate
Bot
force-pushed
the
renovate/major-did-vc-libraries
branch
from
July 21, 2026 02:45
4eb42c4 to
359ecbf
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.0.22→^1.0.0^4.0.0→^7.0.0^4.0.0→^5.0.0^6.0.0→^9.0.0^10.0.0→^12.0.0^7.0.0→^10.0.0^4.1.0→^5.0.0^11.0.2→^13.0.0^6.0.0→^9.0.0Release Notes
aviarytech/did-peer (@aviarytech/did-peer)
v1.1.2Compare Source
Bug Fixes
v1.1.1Compare Source
Bug Fixes
v1.1.0Compare Source
Features
1.0.2 (2025-07-28)
Bug Fixes
1.0.1 (2025-07-28)
Bug Fixes
v1.0.2Compare Source
Bug Fixes
v1.0.1Compare Source
Bug Fixes
v1.0.0Compare Source
Bug Fixes
digitalcredentials/ed25519-signature-2020 (@digitalcredentials/ed25519-signature-2020)
v7.0.0Compare Source
Changed
v6.0.0Compare Source
Changed
@digitalcredentials/jsonld-signatures@12.0.0now requiresexpo-cryptofor React Native sha256 digest hashing, instead of@sphereon/isomorphic-webcrypto@2.5.0-unstable.0.expo-cryptoin your project's
dependencies.v5.0.0Compare Source
Changed
@digitalcredentials/jsonld-signaturesv11.0.0 (latest Sphereon webcrypto fork, latest DCC forks of jsonld and http-client).digitalcredentials/ed25519-verification-key-2020 (@digitalcredentials/ed25519-verification-key-2020)
v5.0.0Compare Source
Changed
@digitalcredentials/keypair@3.0.0and@digitalcredentials/ssi@5.2.0libraries.digitalcredentials/jsonld.js (@digitalcredentials/jsonld)
v9.0.0Compare Source
Changed
@digitalcredentials/jsonld(to fix upstream http-client export error).@digitalcredentials/http-client@5.0.0fork.digitalcredentials/jsonld-signatures (@digitalcredentials/jsonld-signatures)
v12.0.1Compare Source
Fixed
expo-cryptobrowser export.v12.0.0Compare Source
Changed
expo-cryptofor React Native sha256 digest hashing, instead of@sphereon/isomorphic-webcrypto@2.5.0-unstable.0.expo-cryptoin your project's
dependencies.v11.0.0Compare Source
Changed
jsonldandhttp-client.digitalcredentials/vc (@digitalcredentials/vc)
v10.0.2Compare Source
Changed
createPresentationthrowing expiration error whenverify: false.v10.0.1Compare Source
Changed
createPresentationto allow VC verification to be optional.Addresses issue #32. Does not change current default behavior.
v10.0.0Compare Source
Changed
Fixed
v9.0.1Compare Source
Fixed
v9.0.0Compare Source
Changed
@digitalcredentials/jsonld-signatures@12.0.0(via@digitalcredentials/ed25519-signature-2020)now requires
expo-cryptofor React Native sha256 digest hashing, instead of@sphereon/isomorphic-webcrypto@2.5.0-unstable.0.expo-cryptoin your project's
dependencies.v8.0.1Compare Source
Fixed
CredentialIssuancePurpose.v8.0.0Compare Source
Added
validFromandvalidUntil.credentialStatusarrays in credential status check.derive()API for deriving new verifiable credentials fromexisting ones, for the purpose of selective disclosure or
unlinkable presentation.
nowtoverifyCredential(),createPresentation(),verify(), andissue().Changed
@digitalcredentials/jsonld@digitalcredentials/jsonld-signatures@digitalcredentials/http-clientengines.nodeto>=18to support newer keys & suites.expansionMap. (Removed in dependencies.)jsonld-signatures@11andjsonld@8to get newsafemode (and on by default when using
canonize) feature.expirationDatepropertyexists.
did-veres-one@15.0.0used in tests.Fixed
issuanceDateis only checked on verification,not issuance.
Removed
./lib/contexts/andfrom the default document loader. The contexts are now available in
@digitalbazaar/odrl-contextand
@digitalbazaar/credentials-examples-context.decentralized-identity/did-resolver (did-resolver)
v5.0.1Compare Source
Bug Fixes
@contextand verification method types for improved extensibility (#156) (2ad4c48)v5.0.0Compare Source
BREAKING CHANGES
decentralized-identity/ethr-did-resolver (ethr-did-resolver)
v13.1.0Compare Source
Features
13.0.3 (2026-06-22)
Bug Fixes
13.0.2 (2026-06-22)
Bug Fixes
13.0.1 (2026-06-02)
Bug Fixes
v13.0.3Compare Source
Features
13.0.3 (2026-06-22)
Bug Fixes
13.0.2 (2026-06-22)
Bug Fixes
13.0.1 (2026-06-02)
Bug Fixes
v13.0.0Compare Source
Features
13.0.3 (2026-06-22)
Bug Fixes
13.0.2 (2026-06-22)
Bug Fixes
13.0.1 (2026-06-02)
Bug Fixes
v12.0.1Compare Source
Bug Fixes
BREAKING CHANGES
exportsproperty to match new ESM/CJS project layout12.0.1 (2026-05-18)
Bug Fixes
v12.0.0Compare Source
Bug Fixes
BREAKING CHANGES
exportsproperty to match new ESM/CJS project layout12.0.1 (2026-05-18)
Bug Fixes
v11.1.3Compare Source
Features
BREAKING CHANGES
attrTypesanddelegateTypesare 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 2018X25519 => X25519KeyAgreementKey2020
instead of 2019
The #controllerKey is now resolved using
publicKeyJwkinstead ofpublicKeyHexadded 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, andErrorsfeat: 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
11.1.2 (2026-05-04)
Bug Fixes
11.1.1 (2026-05-04)
Bug Fixes
v11.1.2Compare Source
Features
BREAKING CHANGES
attrTypesanddelegateTypesare 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 2018X25519 => X25519KeyAgreementKey2020
instead of 2019
The #controllerKey is now resolved using
publicKeyJwkinstead ofpublicKeyHexadded 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, andErrorsfeat: 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
11.1.2 (2026-05-04)
Bug Fixes
11.1.1 (2026-05-04)
Bug Fixes
v11.1.1Compare Source
Features
BREAKING CHANGES
attrTypesanddelegateTypesare 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 2018X25519 => X25519KeyAgreementKey2020
instead of 2019
The #controllerKey is now resolved using
publicKeyJwkinstead ofpublicKeyHexadded 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, andErrorsfeat: 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
11.1.2 (2026-05-04)
Bug Fixes
11.1.1 (2026-05-04)
Bug Fixes
v11.1.0Compare Source
Features
BREAKING CHANGES
attrTypesanddelegateTypesare 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 2018X25519 => X25519KeyAgreementKey2020
instead of 2019
The #controllerKey is now resolved using
publicKeyJwkinstead ofpublicKeyHexadded 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, andErrorsfeat: 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
11.1.2 (2026-05-04)
Bug Fixes
11.1.1 (2026-05-04)
Bug Fixes
v11.0.5Compare Source
Features
11.0.5 (2025-08-10)
Bug Fixes
11.0.4 (2025-06-13)
Bug Fixes
11.0.3 (2025-01-06)
Bug Fixes
11.0.2 (2024-10-12)
Bug Fixes
11.0.1 (2024-10-01)
Bug Fixes
v11.0.4Compare Source
Features
11.0.5 (2025-08-10)
Bug Fixes
11.0.4 (2025-06-13)
Bug Fixes
11.0.3 (2025-01-06)
Bug Fixes
11.0.2 (2024-10-12)
Bug Fixes
11.0.1 (2024-10-01)
Bug Fixes
Configuration
📅 Schedule: (UTC)
🚦 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.