Renovate v39 not fetching new version in package-lock.json

[vwu-atlassian]

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 run npm i on the branch to get the changes into package-lock.json.

I've tried utilizing postUpdateTasks in our Renovate config and configured it to run npm i when changes to package.json are detected.

"postUpgradeTasks": {
   "commands": ["npm i"],
   "fileFilters": ["package.json"]
 }

1. Renovate updates the version in package.json
2. The postUpgradeTasks runs npm i
3. npm sees the updated version in package.json but isn't fetching the new package. We are only seeing that the old package version is removed from package-lock.json

Logs (if relevant)

Logs

Replace this text with your logs, between the starting and ending triple backticks

[github-actions[bot]]

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:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

If you need help with running renovate on your minimal reproduction repository, please refer to our Running Renovate guide.
Good luck,

The Renovate team

[fdw]

I have the same problem with version 39.185.0. It worked fine a week ago, and no changes in config.

It adds a comment to the PR with the error

The artifact failure details are included below:
File name: <directory>/package-lock.json
undefined

In a later run, I can find this in the debug log:

DEBUG: Getting updated lock files (repository=<repo>, branch=renovate/non-major)
DEBUG: Writing package.json files (repository=<repo>, branch=renovate/non-major)
       "packageFiles": ["<directory>/package.json"]
DEBUG: Writing <directory>/package-lock.json (repository=<repo>, branch=renovate/non-major)
DEBUG: Massaging npm lock file before writing to disk (repository=<repo>, branch=renovate/non-major)
DEBUG: Writing any updated package files (repository=<repo>, branch=renovate/non-major)
DEBUG: Found 1 npm host rule(s) (repository=<repo>, branch=renovate/non-major)
DEBUG: Adding npmrc entry for <private registry> with username/password (repository=<repo>, branch=renovate/non-major)
DEBUG: No updated lock files in branch (repository=<repo>, branch=renovate/non-major)
DEBUG: No changes to package files, skipping post-upgrade tasks (repository=<repo>, branch=renovate/non-major)
DEBUG: No files to commit (repository=<repo>, branch=renovate/non-major)

So it does something with the lock file, but that doesn't change it, and so it is not committed?