Renovate v39 not fetching new version in package-lock.json #34017
Unanswered
vwu-atlassian
asked this question in
Request Help
Replies: 1 comment
-
Hi there, Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible. Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues. Please follow these steps:
If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide. The Renovate team |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
How are you running Renovate?
Self-hosted Renovate
If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.
39.41.0
Please tell us more about your question or problem
How are you running Renovate?
Self-hosted
If you're self-hosting Renovate, tell us what version of Renovate you run.
39.41.0
If you're self-hosting Renovate, select which platform you are using.
bitbucket
Was this something which used to work for you, and then stopped?
It used to work, and then stopped
For two of our repos, Renovate has been generating PRs with only changes to
package.json
. To fix this we've had to manually runnpm i
on the branch to get the changes intopackage-lock.json
.I've tried utilizing
postUpdateTasks
in our Renovate config and configured it to runnpm i
when changes to package.json are detected.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions