Update dependency org.codehaus.plexus:plexus-sec-dispatcher to v4 (master)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
org.codehaus.plexus:plexus-sec-dispatcher (source)	2.0 -> 4.1.0

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[ivy-rew]

seems like renovate doesn't care about my already closed PR's
#579
...any ideas what's wrong @alexsuter

[alexsuter]

Renovate uses the pr title to detect if the PR was already opened before:

Branch name and PR title are cache keys

https://docs.renovatebot.com/key-concepts/pull-requests/

Seems like this PR starts sometime with fix(deps) and sometimes with Update.

I need to further investigate why this happens.

[alexsuter]

Renovate uses the branch name and PR title like a cache key. If the same key exists and the PR was closed, then we ignore the PR.

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

[alexsuter]

@ivy-rew are you sure that this PR get's opened and opened? I've closed it and now it is reported as 'ignore'

[ivy-rew]

Renovate uses the pr title to detect if the PR was already opened before:

Branch name and PR title are cache keys

https://docs.renovatebot.com/key-concepts/pull-requests/

Seems like this PR starts sometime with fix(deps) and sometimes with Update.

I need to further investigate why this happens.

I think we need to find out when and why renovate changes the PR names. I assume here we got into this problem as at creation time the PR titles wasn't matching the old one: 'fix(deps)' vs. 'Update'

[alexsuter]

Did you delete the branch by hand?

[ivy-rew]

Did you delete the branch by hand?

no; just used github web-ui and worked on the PRs