Open mend-for-github-com[bot] opened 2 years ago
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:
The artifact failure details are included below:
Error: Failed to replace env in config: ${GH_NPM_REGISTRY_TOKEN}
at /home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/config/core.js:415:13
at String.replace (<anonymous>)
at envReplace (/home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/config/core.js:411:12)
at parseField (/home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/config/core.js:389:7)
at /home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/config/core.js:330:24
at Array.forEach (<anonymous>)
at Conf.add (/home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/config/core.js:328:23)
at ConfigChain.addString (/home/ubuntu/npm/6.14.16/lib/node_modules/npm/node_modules/config-chain/index.js:244:8)
at Conf.<anonymous> (/home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/config/core.js:316:10)
at /home/ubuntu/npm/6.14.16/lib/node_modules/npm/node_modules/graceful-fs/graceful-fs.js:123:16
/home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/npm.js:59
throw new Error('npm.load() required')
^
Error: npm.load() required
at Object.get (/home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/npm.js:59:13)
at process.errorHandler (/home/ubuntu/npm/6.14.16/lib/node_modules/npm/lib/utils/error-handler.js:208:32)
at process.emit (node:events:390:28)
at process._fatalException (node:internal/process/execution:164:25)
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.
This PR has been flagged for autoclosing. However, it is being skipped due to the branch being already modified. Please close/delete it manually or report a bug if you think this is in error.
This PR contains the following updates:
~2.29.1
->~2.29.4
2.29.1
->2.29.4
By merging this PR, the below issues will be automatically resolved and closed: