Renovate mixing different upgrades in same PR and even downgrades packages

[usu]

There's some strange shenanigan happening with renovate lately. We had several renovate PRs raised that were not automerged for the following reason: "Automerge: Disabled because a matching PR was automerged previously."

See latest example: chore(deps): update tiryoh/gha-jobid-action action to v1.1.0 #4308

The following seems to happen:

Initial PR is raised

chore(deps): update tiryoh/gha-jobid-action action to v1.1.0 #4306 Commits:

• https://github.com/ecamp/ecamp3/pull/4306/commits/c21559ac0db9fef9806afe685278c5aac3649fd3

Merged on Dec23, 8:54 AM GMT+1

A completely different upgrade PR is raised

fix(deps): update dependency isomorphic-dompurify to v2 #4307 Commits:

• https://github.com/ecamp/ecamp3/pull/4307/commits/c21559ac0db9fef9806afe685278c5aac3649fd3
• https://github.com/ecamp/ecamp3/pull/4307/commits/7514801a35f93bf63a594bafebf4563ec6b3178e

The 1st commit is exactly the same commit as for the other PR. Why this is part of this commit is unclear to me. The 2nd commit contains the upgrade of isomorphic-dompurify (expected), but also downgrades gha-jobid-action (very unexpected!).

This PR was merged on Dec23, 10:36 AM GMT+1

New PR is raised for gha-jobid-action

After that, a new PR is raided to upgrade gha-jobid-action again: chore(deps): update tiryoh/gha-jobid-action action to v1.1.0 #4308

[BacLuc]

Can be seen very well with the history for the doctrine/orm package:

[BacLuc]

@usu enabled automatic branch deletion after a PR is merged

[carlobeltrame]

Is this still a problem?

[BacLuc]

Yes, all the time