Update dependency @release-it/keep-a-changelog to v5 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@release-it/keep-a-changelog	4.0.0 -> 5.0.0

---

Release Notes

release-it/keep-a-changelog (@​release-it/keep-a-changelog)

v5.0.0

Compare Source

• Drop support for Node.js v16 + add CI tests (d437d5e)
• Update dependencies (c4671fe)
• Readme addition: Explain what this plugin does (#​34) (59d7ead)

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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 has been generated by Mend Renovate. View repository job log here.

[renovate]

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: sortier@2.0.2
npm ERR! Found: release-it@16.3.0
npm ERR! node_modules/release-it
npm ERR!   dev release-it@"16.3.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer release-it@"^17.0.0" from @release-it/keep-a-changelog@5.0.0
npm ERR! node_modules/@release-it/keep-a-changelog
npm ERR!   dev @release-it/keep-a-changelog@"5.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/renovate/cache/others/npm/_logs/2023-12-24T10_43_08_681Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2023-12-24T10_43_08_681Z-debug-0.log