chore(deps): bump @credo-ts/anoncreds from 0.5.19 to 0.6.2

[dependabot]

Bumps @credo-ts/anoncreds from 0.5.19 to 0.6.2.

Changelog

Sourced from @​credo-ts/anoncreds's changelog.

0.6.2

Patch Changes

• Updated dependencies [b9bd214]
• Updated dependencies [69acbc3]
• Updated dependencies [4a4473c]
• Updated dependencies [2c15356]
• Updated dependencies [4989dd9]
• Updated dependencies [0f7171a]
• Updated dependencies [e441cc1]
• Updated dependencies [1969c67]
• Updated dependencies [620bb38]
• Updated dependencies [2073110]
• Updated dependencies [620bb38]
  • @​credo-ts/core@​0.6.2
  • @​credo-ts/didcomm@​0.6.2

0.6.1

Patch Changes

• Updated dependencies [9f60e1b]
• Updated dependencies [251cbe5]
  • @​credo-ts/core@​0.6.1
  • @​credo-ts/didcomm@​0.6.1

0.6.0

Minor Changes

• 879ed2c: deprecate node 18

• 297d209: - Rely on Uint8Array instead of Buffer for internal key bytes representation

  • Remove dependency on external Big Number libraries
  • Default to use of uncompressed keys for Secp256k1, Secp256r1, Secp384r1 and Secp521r1

• 2cace9c: refactor: remove support for DIDComm linked attachments. The functionality was not working correctly anymore, and only supported for the deprecated v1 issuance protocol

• b5fc7a6: - All didcomm package modules, APIs, models and services that are used for dependency injection now are prefixed with DidComm in its naming

  • DIDComm-related events have also changed their text string to make it possible to distinguish them from events triggered by other protocols
  • DIDComm credentials module API has been updated to use the term credentialExchangeRecord instead of credentialRecord, since it is usually confused with W3cCredentialRecords (and potentially other kind of credential records we might have). I took this opportunity to also update declineOffer options structure to match DIDComm proofs module API
  • DIDComm-related records were renamed, but their type is still the original one (e.g. CredentialRecord, BasicMessageRecord). Probably it's worth to take this major release to do the migration, but I'm afraid that it will be a bit risky, so I'm hesitating to do so or leaving it for some other major upgrade (if we think it's actually needed)

• e936068: when signing in Credo, it is now required to always reference a key id. For DIDs this is extracted from the DidRecord, and for JWKs (e.g. in holder binding) this is extracted form the kid of the JWK. For X509 certificates you need to make sure there is a key id attached to the certificate manually for now, since we don't have a X509 record like we have a DidRecord. For x509 certificates created before 0.6 you can use the legacy key id (certificate.keyId = certificate.publicJwk.legacyKeyId), for certificates created after 0.6 you need to manually store the key id and set it on the certificate after decoding.

  For this reason, we now require instances of X509 certificates where we used to require encoded certificates, to allow you to set the keyId on the certificate beforehand.

• 9f78a6e: upgrade anoncreds wrapper to 0.3

• 2cace9c: The following modules are marked as deprecated and will be removed in version 0.7 of Credo:

  • DIDComm Connection Protocol V1 - Update to the DID Exchange protocol instead.
  • DIDComm V1 Credential Protocol - Update to the DIDComm V2 Credential Protocol instead.
  • DIDComm Legacy Indy Credential Format - Update to the DIDComm AnonCreds Credential Format.
  • DIDComm V1 Proof Protocol - Update to the DIDComm V2 Proof Protocol instead.

... (truncated)

Commits

• 209479e chore(release): new version (#2583)
• 10e6854 chore(deps): bump the patch-updates group across 1 directory with 92 updates ...
• fc7f6a2 fix(cheqd): resolving anoncreds from local record missing metadata (#2640)
• a6e6f72 fix: cheqd registration with caching (#2631)
• ac7f17e chore(release): new version (#2567)
• 9982f17 chore(release): new version (#2091)
• fd70ada feat: support caching for anoncreds resolving (#2550)
• 09ea6e3 fix: allow x25519 key in document (#2541)
• 69ad780 chore: only output ESM (#2539)
• 5ff7bba feat(didcomm): send revocation notification without credex record (#2525)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by [GitHub Actions](https://www.npmjs.com/~GitHub Actions), a new releaser for @​credo-ts/anoncreds since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.