renovate/lock-file-maintenance branch not being autodeleted after automerge

[leaumar]

What Renovate type, platform and version are you using?

free public gitlab bot

Describe the bug

After weekly lock file maintenance with automerge, the renovate/lock-file-maintenance branch remains in my repo despite the bot showing logs for several runs since the automerge. Happens consistently in all of my gitlab repos.
Dependency upgrade branches on the other hand are deleted as expected after automerge.

Relevant debug logs

automerge
after automerge

To Reproduce

public repo

It's a public repo so you can see branches, build logs, etc...

Additional context

n/a

PS: thanks for this great tool :)

[rarkins]

This is essentially "expected behavior" but I'll leave this open in case we can think of a way to do it. Not all lock file maintenance PRs are automerged, but maybe in the case of automerge we could maybe try removing the branch immediately after. Isn't there a feature in GitLab to remove merged head commits anyway?

[leaumar]

How would I expect this behavior if regular dependency upgrade branches do get deleted after automerge?

feature in GitLab to remove merged head commits anyway

That would be extra setup for an ability renovate already has, and I don't think I'd want to enable this since it would affect all branches, not just renovate's.

[rarkins]

Resolution: we should delete our source branches any time we automerge (branch or PR). This will include lock file maintenance.

[rarkins]

Make sure: we don't cause ourselves any unnecessary errors or warnings later when we "prune" branches

[renovate-release]

:tada: This issue has been resolved in version 23.75.0 :tada:

The release is available on:

• GitHub release
• 23.75.0

Your semantic-release bot :package::rocket:

[leaumar]

Confirming it works on my repos since this week, thank you!