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 dependency jscpd to v3 - autoclosed #34

Closed
wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented May 8, 2020

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jscpd 2.0.16 -> 3.5.10 age adoption passing confidence

Release Notes

kucherenko/jscpd (jscpd)

v3.5.10

Compare Source

v3.5.9

Compare Source

v3.5.8

Compare Source

v3.5.6

Compare Source

v3.5.5

Compare Source

v3.5.4

Compare Source

v3.5.3

Compare Source

v3.5.1

Compare Source

v3.5.0

Compare Source

v3.4.5

Compare Source

v3.4.2

Compare Source

v3.4.1

Compare Source

v3.3.26

Compare Source

v3.3.25

Compare Source

v3.3.24

Compare Source

v3.3.23

Compare Source

v3.3.22

Compare Source

v3.3.21

Compare Source

v3.3.20

Compare Source

v3.3.19

Compare Source

v3.3.17

Compare Source

v3.3.16

Compare Source

v3.3.14

Compare Source

v3.3.13

Compare Source

v3.3.11

Compare Source

v3.3.9

Compare Source

v3.3.8

Compare Source

v3.3.3

Compare Source

v3.3.2

Compare Source

v3.3.1

Compare Source

v3.2.1

Compare Source

v3.2.0

Compare Source

Bug Fixes
  • package: update cli-table3 to version 0.6.0 (0b29242)
  • package: update fs-extra to version 9.0.0 (cbae200)
Features
  • detector: skip duplicates in same folder if --skipLocal used (7029ddd), closes #​326

v3.1.0

Compare Source

Features
  • formats: Add ability to find duplications in txt files (0a46e76), closes #​272
3.0.1 (2020-03-10)
Bug Fixes
  • blamer: Fix usage fix of blamer (5f9e125), closes #​238
  • package: update blamer to version 1.0.1 (966fca8)

v3.0.1

Compare Source

v3.0.0

Compare Source

⚠ BREAKING CHANGES
Bug Fixes
  • package: update commander to version 4.0.1 (f36d545)
  • package: update level to version 6.0.0 (374f659)
  • xml reporter: fix issue with CDATA in xml reporter (5643092), closes #​331
Features
  • cli: change cli script for running jscpd (536c44e)
2.0.16 (2019-09-24)
Bug Fixes
  • .snyk, package.json & package-lock.json to reduce vulnerabilities (5fddd70)
  • package: update commander to version 3.0.0 (c41cf11)
  • package: update eventemitter3 to version 4.0.0 (cadd3ab)
  • package: update fs-extra to version 8.0.0 (a1c3936)
  • package: update rimraf to version 3.0.0 (47afcca)
  • package: update snyk to version 2.0.0 (30828ee)
  • readme: fix typo in readme (a49b801)
  • readme: fixes screenshot url (ee6fd67)
  • snap: fix tests snapshots (cc6402d)

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.

🔕 Ignore: Close this PR and you won't be reminded about this update 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
Copy link
Author

renovate bot commented Sep 17, 2023

⚠ 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 WARN old lockfile 
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile 
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile 
npm WARN old lockfile badgen: No matching version found for badgen@2.9.0.
npm WARN old lockfile     at module.exports (/opt/containerbase/tools/npm/10.1.0/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
npm WARN old lockfile     at RegistryFetcher.manifest (/opt/containerbase/tools/npm/10.1.0/node_modules/npm/node_modules/pacote/lib/registry.js:119:22)
npm WARN old lockfile     at async Array.<anonymous> (/opt/containerbase/tools/npm/10.1.0/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:727:24)
npm WARN old lockfile  Could not fetch metadata for badgen@2.9.0 badgen: No matching version found for badgen@2.9.0.
npm WARN old lockfile     at module.exports (/opt/containerbase/tools/npm/10.1.0/node_modules/npm/node_modules/npm-pick-manifest/lib/index.js:209:23)
npm WARN old lockfile     at RegistryFetcher.manifest (/opt/containerbase/tools/npm/10.1.0/node_modules/npm/node_modules/pacote/lib/registry.js:119:22)
npm WARN old lockfile     at async Array.<anonymous> (/opt/containerbase/tools/npm/10.1.0/node_modules/npm/node_modules/@npmcli/arborist/lib/arborist/build-ideal-tree.js:727:24) {
npm WARN old lockfile   code: 'ETARGET',
npm WARN old lockfile   type: 'version',
npm WARN old lockfile   wanted: '2.9.0',
npm WARN old lockfile   versions: [
npm WARN old lockfile     '0.1.0', '0.2.0', '0.2.1', '0.2.2',
npm WARN old lockfile     '0.3.0', '1.0.0', '1.0.1', '1.1.0',
npm WARN old lockfile     '1.1.1', '1.1.2', '1.1.3', '1.1.4',
npm WARN old lockfile     '1.2.0', '2.0.0', '2.1.0', '2.1.1',
npm WARN old lockfile     '2.1.2', '2.1.3', '2.1.4', '2.2.0',
npm WARN old lockfile     '2.2.1', '2.2.2', '2.2.3', '2.3.0',
npm WARN old lockfile     '2.3.1', '2.4.0', '2.4.1', '2.4.2',
npm WARN old lockfile     '2.4.3', '2.4.4', '2.4.5', '2.5.0',
npm WARN old lockfile     '2.6.0', '2.7.0', '2.7.1', '2.8.0',
npm WARN old lockfile     '2.8.1', '2.8.2', '3.0.0', '3.0.1',
npm WARN old lockfile     '3.1.0', '3.2.0', '3.2.1', '3.2.2',
npm WARN old lockfile     '3.2.3'
npm WARN old lockfile   ],
npm WARN old lockfile   distTags: { latest: '3.2.3' },
npm WARN old lockfile   defaultTag: 'latest'
npm WARN old lockfile }
npm WARN ERESOLVE overriding peer dependency
npm WARN While resolving: @js-items/ky@0.0.0-development
npm WARN Found: jscpd@2.0.16
npm WARN node_modules/jscpd
npm WARN   jscpd@"3.5.10" from the root project
npm WARN   1 more (@js-items/foundation)
npm WARN 
npm WARN Could not resolve dependency:
npm WARN peer jscpd@"1.0.0-rc.6" from jscpd-badge-reporter@1.1.3
npm WARN node_modules/jscpd-badge-reporter
npm WARN   jscpd-badge-reporter@"1.1.3" from the root project
npm WARN   1 more (@js-items/foundation)
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: @js-items/ky@0.0.0-development
npm ERR! Found: jscpd@3.5.10
npm ERR! node_modules/jscpd
npm ERR!   jscpd@"3.5.10" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer jscpd@"1.0.0-rc.6" from jscpd-badge-reporter@1.1.3
npm ERR! node_modules/jscpd-badge-reporter
npm ERR!   jscpd-badge-reporter@"1.1.3" 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/cc6598/ef0c16/cache/others/npm/_logs/2023-09-17T21_22_09_699Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/cc6598/ef0c16/cache/others/npm/_logs/2023-09-17T21_22_09_699Z-debug-0.log

@renovate renovate bot changed the title fix(deps): update dependency jscpd to v3 fix(deps): update dependency jscpd to v3 - autoclosed May 26, 2024
@renovate renovate bot closed this May 26, 2024
@renovate renovate bot deleted the renovate/jscpd-3.x branch May 26, 2024 16:52
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.

None yet

0 participants