You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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."
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!).
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:
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:
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
The text was updated successfully, but these errors were encountered: