compiled icon indicating copy to clipboard operation
compiled copied to clipboard

chore(deps): lock file maintenance

Open renovate[bot] opened this issue 4 years ago • 3 comments

Mend Renovate

This PR contains the following updates:

Update Change
lockFileMaintenance All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.


Configuration

📅 Schedule: Branch creation - "before 5am on monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled due to failing status checks.

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, click this checkbox.

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

renovate[bot] avatar May 17 '21 04:05 renovate[bot]

⚠️ No Changeset found

Latest commit: 836328339b44d2d38d44436536758393a079e9fd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

changeset-bot[bot] avatar May 17 '21 04:05 changeset-bot[bot]

⚠ Artifact update problem

Renovate failed to update artifacts 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: fixtures/parcel-transformer-test-extract-app/package-lock.json
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-transformer-test-extract-app/.npmrc 
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-transformer-test-extract-app/.npmrc 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^29.4.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^26.0.0 || ^27.0.0" from [email protected]
npm ERR! node_modules/jest-watch-typeahead
npm ERR!   dev jest-watch-typeahead@"^0.6.5" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_11_563Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_11_563Z-debug-0.log

File name: fixtures/parcel-transformer-test-custom-resolver-app/package-lock.json
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-transformer-test-custom-resolver-app/.npmrc 
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-transformer-test-custom-resolver-app/.npmrc 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^29.4.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^26.0.0 || ^27.0.0" from [email protected]
npm ERR! node_modules/jest-watch-typeahead
npm ERR!   dev jest-watch-typeahead@"^0.6.5" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_21_551Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_21_551Z-debug-0.log

File name: fixtures/parcel-transformer-test-custom-resolve-app/package-lock.json
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-transformer-test-custom-resolve-app/.npmrc 
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-transformer-test-custom-resolve-app/.npmrc 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^29.4.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^26.0.0 || ^27.0.0" from [email protected]
npm ERR! node_modules/jest-watch-typeahead
npm ERR!   dev jest-watch-typeahead@"^0.6.5" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_31_467Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_31_467Z-debug-0.log

File name: fixtures/parcel-transformer-test-compress-class-name-app/package-lock.json
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-transformer-test-compress-class-name-app/.npmrc 
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-transformer-test-compress-class-name-app/.npmrc 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^29.4.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^26.0.0 || ^27.0.0" from [email protected]
npm ERR! node_modules/jest-watch-typeahead
npm ERR!   dev jest-watch-typeahead@"^0.6.5" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_41_385Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_41_385Z-debug-0.log

File name: fixtures/parcel-optimizer-test-app/package-lock.json
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-optimizer-test-app/.npmrc 
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/fixtures/parcel-optimizer-test-app/.npmrc 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^29.4.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^26.0.0 || ^27.0.0" from [email protected]
npm ERR! node_modules/jest-watch-typeahead
npm ERR!   dev jest-watch-typeahead@"^0.6.5" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_51_448Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T22_59_51_448Z-debug-0.log

File name: examples/parcel/package-lock.json
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/examples/parcel/.npmrc 
npm WARN ignoring workspace config at /tmp/worker/58a705/962bb5/repos/github/atlassian-labs/compiled/examples/parcel/.npmrc 
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: [email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/jest
npm ERR!   dev jest@"^29.4.3" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jest@"^26.0.0 || ^27.0.0" from [email protected]
npm ERR! node_modules/jest-watch-typeahead
npm ERR!   dev jest-watch-typeahead@"^0.6.5" 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! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T23_00_01_654Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/58a705/962bb5/cache/others/npm/_logs/2023-10-19T23_00_01_654Z-debug-0.log

renovate[bot] avatar Mar 22 '22 03:03 renovate[bot]

Thank you for your submission! Like many open source projects, we ask that you sign our CLA (Contributor License Agreement) before we can accept your contribution. If your email is listed below, please ensure that you sign the CLA with the same email address. The following users still need to sign our CLA:❌renovate[bot]

Already signed the CLA? To re-check, try refreshing the page.

atlassian-cla-bot[bot] avatar Jul 11 '22 00:07 atlassian-cla-bot[bot]

Closing as stale.

itsdouges avatar Oct 22 '23 22:10 itsdouges