chore(deps): update dependency release-it to v20

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
release-it	^19.2.4 → ^20.2.0

---

Release Notes

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

v20.2.0

Compare Source

• Print staged-packages approval URL after stage publish (244d811)
• Capture the stage id for the approval message (2476065)

v20.1.0

Compare Source

• feat: add --quiet flag to hide release previews (#​1274) (ecefe44) - thanks @​Yeom-JinHo!
• fix: ensure release body is an empty string instead of null (#​1303) (5cc5ebd) - thanks @​driiftkiing!
• Add 'Accept-Encoding' header to GitLab API requests (#​1301) (14a478e) - thanks @​KlausDerKleber!
• Support npm staged publishing (npm.stage) (aa20f56)
• Run tests on Node 26 (29f079b)
• Use draft flow for immutable releases with assets (resolve #​1295) (c63b4e4)
• Publish interactively under --only-version so passkey 2FA works (resolve #​1234) (4ebb66e)
• Format docs/npm.md (a2a262c)
• Dogfoodin' (0cb51a9)

v20.0.1

Compare Source

• fix: allow false as npm config value in types (#​1289) (f783e82) - thanks @​ahippler!
• Bump actions/checkout from 5 to 6 (#​1262) (19921fc) - thanks @​dependabot[bot]!
• fix: Replace @​nodeutils/defaults-deep with defu for deep-default merging (#​1297) (8616a21) - thanks @​rajnsunny!
• Update dependencies (bee3138)

v20.0.0

Compare Source

• fix: remove leading slashes from owner (#​1288) (5585b72) - thanks @​driiftkiing!
• Fix write: false guard in npm.bump (resolve #​1267) (a2d1b99)
• Format (f427a85)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• 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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	release-it@​19.2.4 ⏵ 20.2.0				+1

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm powershell-utils is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/release-it@20.2.0 → npm/powershell-utils@0.1.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/powershell-utils@0.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm powershell-utils is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: package-lock.json → npm/release-it@20.2.0 → npm/powershell-utils@0.2.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/powershell-utils@0.2.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report