Renovate PRs revert previous Renovate upgrades

[josiah-roberts]

What would you like help with?

I think I found a bug

How are you running Renovate?

Mend Renovate hosted app on github.com

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

No response

Please tell us more about your question or problem

Renovate PRs revert previously-merged package-lock.json upgrades from other Renovate PRs.

For example, we previously merged a Renovate PR to upgrade MDX editor. The graphql-http PR reverts that change.

This happens even if we have Renovate rebase the new, graphql-http PR.

Logs (if relevant)

Select me to see logs

INFO: Repository started
{
  "renovateVersion": "37.351.2"
}

INFO: Dependency extraction complete
{
  "baseBranch": "main"
  "stats": {
    "managers": {
      "docker-compose": {
        "fileCount": 1,
        "depCount": 5
      },
      "dockerfile": {
        "fileCount": 3,
        "depCount": 4
      },
      "github-actions": {
        "fileCount": 2,
        "depCount": 12
      },
      "npm": {
        "fileCount": 25,
        "depCount": 390
      },
      "nvm": {
        "fileCount": 1,
        "depCount": 1
      }
    },
    "total": {
      "fileCount": 32,
      "depCount": 412
    }
  }
}

INFO: Branch updated (branch="renovate/graphql-http-1.x-lockfile")
{
  "commitSha": "349ba353c17455ec224fb089078f56db7e1a115f"
}

INFO: PR updated (branch="renovate/graphql-http-1.x-lockfile")
{
  "pr": 405
  "prTitle": "Update dependency graphql-http to v1.22.1"
}

INFO: Repository finished
{
  "cloned": true
  "durationMs": 83197
}

[github-actions[bot]]

Hi there,

This issue or discussion is missing some logs, making it difficult or impossible to help you. Depending on which situation applies follow one, some or all of these instructions.

No logs at all

If you haven't posted any log yet, we need you to find and copy/paste the log into the issue template.

Finding logs on hosted app

Select me to read instructions

If you use the Mend Renovate app (GitHub):

1. Log in to the Mend Developer Portal
2. Navigate to the correct organization and repository
3. Locate the appropriate log (it may not always be the latest one)
4. Copy/paste the log contents
5. Follow the steps in the formatting your logs section

Finding logs when self-hosting

Select me to read instructions

Read the Renovate docs, troubleshooting, self-hosted to learn how to find the logs.

Insufficient logs

Select me to read instructions

If you already gave us a log, and the Renovate team said it's not enough, then follow the instructions from the No logs at all section.

Formatting your logs

Select me to read instructions

Please put your logs in a <details> and <summary> element like this:

<details><summary>Select me to see logs</summary>

```
Copy/paste your logs here, between the starting and ending backticks
```

</details>

If you feel the logs are too large to paste here, please use a service like GitHub Gist and paste the link here.

Good luck,

The Renovate team

[rarkins]

Needs to be debug

[josiah-roberts]

For context, this happens on every single Renovate PR in our Turborepo. This pretty much renders Renovate useless to us.

[rarkins]

Are you able to fetch debug logs?

[josiah-roberts]

Ah, I didn't realize that you were asking a question.

I can't share the Renovate debug logs here on the public internet, because they contain a variety of sensitive pieces of information that I don't want to expose. Is there a non-public way I can get them to you?

[rarkins]

Only if you're a customer with a support contract. Otherwise you need to sanitize the logs to post here or create a public reproduction so it's not confidential