Closed cypressious closed 3 years ago
Your reproduction repository does not reproduce for me: https://github.com/renovate-tests/renovate-npm7-issue/pulls
Please generate PRs yourself to verify.
BTW you should not need to use constraints
or force
in your renovate.json
at all.
Hi there,
The Renovate team needs your help! Before we can start work on your issue we first need to know exactly what's causing the current behavior. A minimal reproduction helps us with this.
To get started, please read our guide on minimal reproductions to understand what is needed.
We may close the issue if you have not provided a minimal reproduction within two weeks. If you need more time, or are stuck, please ask for help or more time in a comment.
Good luck,
The Renovate team
We're using GitLab CI on a Self-Hosted GitLab instance where I'm able to reproduce on the given sample, so I'm assuming it has something to do with it.
Simply remove force
and constraints
from config and it should work work, renovate will use the engines
from package.json
@viceice That's what we had initially when the issue started occuring, so it doesn't seem to help.
@cypressious You need to use the dind version, because we have node v14 with npm v6 preinstalled on the full renovate image.
Your other option is to downgrade to npm v6 if you can't use dind.
@viceice Can you point me to a documentation on how to use the didn version? Thanks
constraints are only working when using renovate with binarySource=docker
otherwise renovate can only use global installed tools.
So another options is to build your own renovate image and install npm v7 ontop the default image
@viceice Can you point me to a documentation on how to use the didn version? Thanks
https://gitlab.com/renovate-bot/renovate-runner
We have ready to use templates there
What Renovate type, platform and version are you using?
We're using Renovate on a private GitLab via GitLab CI.
Out
templates/renovate.gitlab-ci.yml
file looks as follows:Describe the bug
We have a Frontend project that we've recently upgraded to npm 7 which comes with a new
package-lock.json
format signified by the"lockfileVersion": 2
line.Every Merge Request by Renovate now wants to revert the
package-lock.json
file back to"lockfileVersion": 1
resulting in a giant diff which we can't merge because we want to stay on"lockfileVersion": 2
.Relevant debug logs
Have you created a minimal reproduction repository?
Minimal Reproduction Example: https://github.com/cypressious/renovate-npm7-issue. Note that the issue happens on GitLab, GitHub is only used for hosting the example.
Additional context
I've tried a number of variations of
constraints
andforce
options in therenovate.json
. The current version is the following but the issue persists: