Closed kochen closed 4 years ago
To Reproduce As it seems, the project was so far updated with
npm v6
or at least had alockfileVersion@1
:
- Manually downgrade
@nrwal/workspace
(inpackages.json
) to be not the latest version- Update the
packages-lock.json
accordingly withnpm v7
- Run
renovate
The issue was related to the manual/local refresh of the lock file with a different node (15) and npm (7) version.
What Renovate type, platform and version are you using? We are using GitLab (CI) self-hosted version: 23.84.3 (latest of of this moment)
Describe the bug We are trying to mak use of the new
postUpgradeTasks
for ournx
based project and we execute these commands:Relevant debug logs
To Reproduce As it seems, the project was so far updated with
npm v6
or at least had alockfileVersion@1
:@nrwal/workspace
(inpackages.json
) to be not the latest versionpackages-lock.json
accordingly withnpm v7
renovate
This will result in:
Additional context
Is there a way to "force" renovate to use the newly added
npm v7
? See renovatebot/renovate#7700