Skip to content

fix(deps): update veramo-dependencies to v6 (major)#30

Open
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-veramo-dependencies
Open

fix(deps): update veramo-dependencies to v6 (major)#30
renovate[bot] wants to merge 1 commit intomainfrom
renovate/major-veramo-dependencies

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Apr 3, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@veramo/core-types (source) ^5.1.2 -> ^6.0.0 age adoption passing confidence
@veramo/did-manager (source) ^5.1.2 -> ^6.0.0 age adoption passing confidence
@veramo/key-manager (source) ^5.1.2 -> ^6.0.0 age adoption passing confidence

Release Notes

decentralized-identity/veramo (@​veramo/core-types)

v6.0.0

Compare Source

Bug Fixes
chore
Code Refactoring
Features
BREAKING CHANGES
  • did-comm: the DIDComm Message structure has changed. The message can now specify multiple recipients in the to property.
  • utils: The getChainIdForDidEthr method has been renamed to getChainId
  • The plugin.schema.json files are now generated as plugin.schema.ts.
  • did-comm: the return type of IDIDComm.sendDIDCommMessage() has changed from a string representing the transport ID to an object that may include a returnMessage property along with a transportId property.
  • did-manager: The behavior of DIDManager has changed when working with alias. It is mostly ignoring provider unless it is used to create new identifiers. AbstractDIDStore APIs have been adapted and implementations have changed.
  • deps: now using ethers v6 as a dependency which may need extra attention when merging. The output of eth_signTransaction algorithms may be slightly different as transactions are by default infered as type 1 (EIP1559)
  • data-store: going forward credentials and presentations will have a new ID format in the database. If you are relying on the IDs assigned internally by @veramo/data-store to work with your credentials, you will have to recompute them using the @veramo/utils#computeEntryHash method.

v5.6.0

Compare Source

Features

5.5.3 (2023-10-09)

Bug Fixes

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.


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

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate Bot added the maintenance label Apr 3, 2024
@renovate
Copy link
Copy Markdown
Contributor Author

renovate Bot commented Apr 3, 2024

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants