Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix(deps): update crypto packages #233

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Mar 16, 2021

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@​arkecosystem/crypto 3.0.0 -> 3.9.1 age adoption passing confidence
@protokol/client (source) 1.0.0-beta.42 -> 1.0.0 age adoption passing confidence
@protokol/nft-base-crypto (source) 1.0.0 -> 1.0.1 age adoption passing confidence
@protokol/nft-exchange-crypto (source) 1.0.0 -> 1.0.1 age adoption passing confidence

Release Notes

protokol/commons (@​protokol/client)

v1.0.0

Compare Source

21 September 2021

protokol/nft-plugins (@​protokol/nft-base-crypto)

v1.0.1

Compare Source

28 September 2021

  • fix(nft-base-api): fix assets transformer #354
  • fix(nft-base-crypto): fix import #355
  • release: 1.0.0 #353

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, 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 renovate bot force-pushed the renovate/crypto-packages branch from fcafb22 to d4cd12f Compare March 16, 2021 13:22
@renovate renovate bot changed the title fix(deps): update crypto packages to v1.0.0-beta.59 fix(deps): update crypto packages Mar 16, 2021
@renovate renovate bot force-pushed the renovate/crypto-packages branch from d4cd12f to 79b152c Compare March 22, 2021 09:22
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 79b152c to 0c9593d Compare April 7, 2021 09:00
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 0c9593d to 74ac4a7 Compare May 5, 2021 09:56
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 74ac4a7 to 848a9c6 Compare May 15, 2021 19:36
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 848a9c6 to 8000c44 Compare June 6, 2021 22:51
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 8000c44 to 1e3a01a Compare June 16, 2021 13:11
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 1e3a01a to 6449294 Compare October 7, 2021 10:09
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 6449294 to 1ca946e Compare March 7, 2022 09:24
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 1ca946e to ce58d19 Compare March 26, 2022 12:28
@renovate renovate bot force-pushed the renovate/crypto-packages branch from ce58d19 to 5d68fbd Compare April 24, 2022 21:43
@renovate
Copy link
Contributor Author

renovate bot commented Apr 24, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jsoneditor
npm ERR!   jsoneditor@"^9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jsoneditor@"^7.0.2" from [email protected]
npm ERR! node_modules/ang-jsoneditor
npm ERR!   ang-jsoneditor@"^1.10.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/jsoneditor
npm ERR!   peer jsoneditor@"^7.0.2" from [email protected]
npm ERR!   node_modules/ang-jsoneditor
npm ERR!     ang-jsoneditor@"^1.10.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-02-02T13_40_56_583Z-debug-0.log

@renovate renovate bot force-pushed the renovate/crypto-packages branch from 4502e8b to f0f1033 Compare March 30, 2023 08:08
@renovate renovate bot force-pushed the renovate/crypto-packages branch 2 times, most recently from 90c0085 to 067d13e Compare July 12, 2023 12:03
@renovate renovate bot force-pushed the renovate/crypto-packages branch from 067d13e to bdb1d98 Compare July 25, 2023 14:22
@renovate renovate bot force-pushed the renovate/crypto-packages branch from f17c5b4 to 9beb11e Compare June 19, 2024 14:49
Copy link
Contributor Author

renovate bot commented Jun 19, 2024

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jsoneditor
npm ERR!   jsoneditor@"^9.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jsoneditor@"^7.0.2" from [email protected]
npm ERR! node_modules/ang-jsoneditor
npm ERR!   ang-jsoneditor@"^1.10.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/jsoneditor
npm ERR!   peer jsoneditor@"^7.0.2" from [email protected]
npm ERR!   node_modules/ang-jsoneditor
npm ERR!     ang-jsoneditor@"^1.10.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2024-06-19T14_48_52_476Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants