chore(deps): update dependency danger to v13

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
danger	13.0.4 → 13.0.5

---

Release Notes

danger/danger-js (danger)

v13.0.5

Compare Source

v13.0.4

Compare Source

---

Fun sidenote, it's been exactly a year and we had to update the node version etc

v13.0.3

Compare Source

• Lots of deploy faff, as we are forced to update node in all the build processing [@​orta]

v13.0.2

Compare Source

v13.0.1

Compare Source

v13.0.0

Compare Source

• Breaking Update @octokit/rest from 18 to 20 to prevent transitive CVEs - Fixes #​1479 [@​fbartho]
• Clean up dead discussion link - Fixes #​1467 [@​fbartho]
• Adds infra for pythons pre-commit hooks
• Replace parse-git-config with ini + fs as it has a CVE out - #​1486
• Disabled Windows CI as it was failing for successful builds

---

Configuration

📅 Schedule: Branch creation - "every weekday" in timezone Etc/UTC, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled because a matching PR was automerged previously.

♻ 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.

[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 could not resolve
npm ERR! 
npm ERR! While resolving: @scaleleap/[email protected]
npm ERR! Found: [email protected]
npm ERR! node_modules/eslint-plugin-unicorn
npm ERR!   dev eslint-plugin-unicorn@"62.0.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! dev eslint-plugin-unicorn@"62.0.0" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: [email protected]
npm ERR! node_modules/eslint
npm ERR!   peer eslint@">=9.38.0" from [email protected]
npm ERR!   node_modules/eslint-plugin-unicorn
npm ERR!     dev eslint-plugin-unicorn@"62.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! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-02-02T21_08_08_641Z-debug-0.log