chore(deps-dev): bump danger from 13.0.4 to 13.0.8

[dependabot]

Bumps danger from 13.0.4 to 13.0.8.

Changelog

Sourced from danger's changelog.

Main

The Docker image behind the Danger GitHub Action now runs on node 22 instead of node 20. The image had stopped building entirely after the recent binary changes, so this gets the action publishing again. - [@​orta]

14.0.7

The Docker image behind the Danger GitHub Action now runs on node 22 instead of node 20. The image had stopped building entirely after the recent binary changes, so this gets the action publishing again. - [@​orta]

14.0.6

The prebuilt macOS binaries (what brew install danger/tap/danger-js gives you) now embed node 24 instead of node 18. Those binaries ship their own copy of node, and the old one was too old for the networking library Danger uses, so every call to GitHub failed with TypeError: terminated. They work again. - [@​orta]

14.0.0-5

Release faff as I migrate to OIDC deploys for danger - orta

14.0.0

Danger now installs undici 7 by default. undici is what Danger uses to talk to GitHub, GitLab and Bitbucket, and version 7 requires node 20.18.1 or newer — so for most people that is Danger's new effective minimum. Node 18 has not been dropped: you can pin undici back to the 6.x line yourself and everything keeps working. - [@​orta]

The reason for the switch is that it puts you in control of your own undici version. Previously Danger pinned undici to the 6.x line, so if a security advisory landed you had to wait for a Danger release to pick up the fix. undici is now an optional peer dependency accepting ^6.28.0 || ^7, which means moving it in either direction is a supported thing to do rather than a workaround.

• github.reviews now reports the review states GitHub actually sends, so checking for a review that requested changes works - fixes #1443 [@​Socialpranker]

... (truncated)

Commits

• 58355dc Release 13.0.8
• ed3f089 Fix up the JSON schema process which was blocking deploys
• 4ea156e Merge pull request #1513 from danger/danger-exec
• 087a729 Adds a fix for a potential local shell execution based on a filename - thanks...
• a9f198a Merge pull request #1509 from glensc/build-sequence
• af06dbf Merge branch 'main' into build-sequence
• 0a438e3 Merge pull request #1508 from glensc/scripts-fail
• e3be890 Move chmod danger.js to build
• 58e96f3 Use && to fail on scripts on error
• d38955b Note otp
• Additional commits viewable in compare view

Install script changes

This version adds prepare script that runs during installation. Review the package contents before updating.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[azure-pipelines]

Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.