Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Mar 30, 2023

This PR contains the following updates:

Package Change Age Confidence
npm (source) 6.14.6 -> 6.14.18 age confidence

Release Notes

npm/cli (npm)

v6.14.18

Compare Source

6.14.18 (2022-12-21)

DEPENDENCIES

v6.14.17

Compare Source

6.14.17 (2022-04-28)

DEPENDENCIES

v6.14.16

Compare Source

6.14.16 (2022-01-19)

CHORE
DEPENDENCIES

v6.14.15

Compare Source

6.14.15 (2021-08-23)

DEPENDENCIES

v6.14.14

Compare Source

6.14.14 (2021-07-27)

DEPENDENCIES

v6.14.13

Compare Source

6.14.13 (2021-04-08)

DEPENDENCIES

v6.14.12

Compare Source

6.14.12 (2021-03-25)

DEPENDENCIES

v6.14.11

Compare Source

6.14.11 (2021-01-07)

DEPENDENCIES
DOCUMENTATION
TESTING

v6.14.10

Compare Source

6.14.10 (2020-12-18)

DEPENDENCIES

v6.14.9

Compare Source

6.14.9 (2020-11-20)

BUG FIXES
  • 4a91e48aa fix: docs generation breaking builds
DEPENDDENCIES

v6.14.8

Compare Source

6.14.8 (2020-08-17)

BUG FIXES
DOCUMENTATION
DEPENDENCIES

v6.14.7

Compare Source

BUG FIXES
DEPENDENCIES

Configuration

📅 Schedule: Branch creation - "after 7am and before 11am every weekday" in timezone Europe/London, 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 was generated by Mend Renovate. View the repository job log.

@renovate
Copy link
Author

renovate bot commented Mar 30, 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
No /opt/buildpack/tools/node/6.17.1/bin/npx defined - aborting
npm ERR! Linux 5.15.0-1023-aws
npm ERR! argv "/opt/buildpack/tools/node/6.17.1/bin/node" "/usr/local/bin/npm" "install" "--package-lock-only" "--no-audit" "--ignore-scripts" "npm@6.14.18"
npm ERR! node v6.17.1
npm ERR! npm  v3.10.10
npm ERR! path /tmp/worker/2e6a69/258908/repos/github/hmcts/cmc-prototype/node_modules/.staging/@iarna/cli-0f968d64
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall rename

npm ERR! enoent ENOENT: no such file or directory, rename '/tmp/worker/2e6a69/258908/repos/github/hmcts/cmc-prototype/node_modules/.staging/@iarna/cli-0f968d64' -> '/tmp/worker/2e6a69/258908/repos/github/hmcts/cmc-prototype/node_modules/npm/node_modules/@iarna/cli'
npm ERR! enoent ENOENT: no such file or directory, rename '/tmp/worker/2e6a69/258908/repos/github/hmcts/cmc-prototype/node_modules/.staging/@iarna/cli-0f968d64' -> '/tmp/worker/2e6a69/258908/repos/github/hmcts/cmc-prototype/node_modules/npm/node_modules/@iarna/cli'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent 

npm ERR! Please include the following file with any support request:
npm ERR!     /tmp/worker/2e6a69/258908/repos/github/hmcts/cmc-prototype/npm-debug.log
npm ERR! code 1

@renovate renovate bot force-pushed the renovate/npm-6.x-lockfile branch from 98ffc60 to a220061 Compare August 14, 2025 19:58
@renovate renovate bot force-pushed the renovate/npm-6.x-lockfile branch from a220061 to 8ae171d Compare November 19, 2025 07:39
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