chore(deps): update dependency release-it to v16 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
release-it	^15.10.1 -> ^16.0.0

---

Release Notes

release-it/release-it (release-it)

v16.1.2

Compare Source

• Revert some updates for Node.js 16 compat (a106c83)

v16.1.1

Compare Source

• Update dependencies (closes #​1023) (9d6f183)

v16.1.0

Compare Source

• Edit and move new section about getLatestTagFromAllRefs up in docs (a166ab4)
• Extend test for getLatestTagFromAllRefs to assert default behavior too (930e80a)
• test: add a test scenario for git.getLatestTagFromAllRefs (fef97c6)
• feat: add git.getLatestTagFromAllRefs config item to use all refs to determine latest version, not just reachable commits. (8611ef0)
• docs: update legacy Node comment on readme page (#​1021) (5beacf2)

v16.0.0

Compare Source

• Add v16 to changelog (2e09260)
• Add knip to deps/scripts (00220ce)
• Update dependencies + add lockfile (breaking support for Node.js v14/npm v6) (97c233e)

---

Configuration

📅 Schedule: Branch creation - "every 3 months on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

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

♻ Rebasing: Whenever PR is behind base branch, 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

/usr/local/bin/docker: line 4: .: filename argument required
.: usage: . filename [arguments]
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @release-it/conventional-changelog@5.1.1
npm ERR! Found: release-it@16.1.2
npm ERR! node_modules/release-it
npm ERR!   dev release-it@"^16.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer release-it@"^15.4.1" from @release-it/conventional-changelog@5.1.1
npm ERR! node_modules/@release-it/conventional-changelog
npm ERR!   dev @release-it/conventional-changelog@"^5.1.1" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: release-it@15.11.0
npm ERR! node_modules/release-it
npm ERR!   peer release-it@"^15.4.1" from @release-it/conventional-changelog@5.1.1
npm ERR!   node_modules/@release-it/conventional-changelog
npm ERR!     dev @release-it/conventional-changelog@"^5.1.1" 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! See /tmp/worker/07f1e3/0e2d11/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/worker/07f1e3/0e2d11/cache/others/npm/_logs/2023-07-16T20_33_19_366Z-debug-0.log