Bump danger from 11.3.1 to 12.2.0

[dependabot[bot]]

Bumps danger from 11.3.1 to 12.2.0.

Release notes

Sourced from danger's releases.

Release 12.2.0

No release notes provided.

Release 12.1.0

It's been 7 years since I looked at danger init and err, the world of CI has changed quite a bit since then. So, Danger JS's init command now knows that GitHub Actions exists and will correctly offer some advice on how to set up a Dangerfile for it. - [@​orta]

---

12.0.1

Bumping to 12.x because we've raised the minimum to node version from 14 to 18. This is due to some of our dependencies requiring a newer version of node. This is a breaking change for some folk! Also, 14 has been out of support for quite a while now and Node 18 gives us a full year. - [@​orta]

• Remove the user checks in GitHub comment/inline comment lookups, to allow using app tokens #1433 - [@​orta]
• Upgrade node engine from >=14.13.1 to >=18 [@​heltoft]
• Upgrade @types/node from ^10.11.3 to 18.19.18 [@​heltoft]
• GitLab: #1386 Move from @gitbeaker/node to @gitbeaker/rest [@​heltoft]
• GitLab: #1412 Danger fails to create inline comments on Gitlab [@​heltoft]
• GitLab: #1405 Can't post multiple inline comments [@​heltoft]
• GitLab: Do not delete system resolved danger inline comments [@​heltoft]
• Fix for ESM imports in Dangerfiles [@​mgol]

Release 12.0.1

Bumping to 12.x because we've raised the minimum to node version from 14 to 18. This is due to some of our dependencies requiring a newer version of node. This is a breaking change for some folk! Also, 14 has been out of support for quite a while now and Node 18 gives us a full year. - [@​orta]

• Remove the user checks in GitHub comment/inline comment lookups, to allow using app tokens #1433 - [@​orta]
• Upgrade node engine from >=14.13.1 to >=18 [@​heltoft]
• Upgrade @types/node from ^10.11.3 to 18.19.18 [@​heltoft]
• GitLab: #1386 Move from @gitbeaker/node to @gitbeaker/rest [@​heltoft]
• GitLab: #1412 Danger fails to create inline comments on Gitlab [@​heltoft]
• GitLab: #1405 Can't post multiple inline comments [@​heltoft]
• GitLab: Do not delete system resolved danger inline comments [@​heltoft]
• Fix for ESM imports in Dangerfiles [@​mgol]

Changelog

Sourced from danger's changelog.

12.2.0

• Adds a log when you run on GitHub Actions without being a pull_request - [@​orta]
• GitHub: Move to 'List pull request files' API with pagination support [@​fabianehlert]

12.1.0

It's been 7 years since I looked at danger init and err, the world of CI has changed quite a bit since then. So, Danger JS's init command now knows that GitHub Actions exists and will correctly offer some advice on how to set up a Dangerfile for it. - [@​orta]

12.0.0

Bumping to 12.x because we've raised the minimum to node version from 14 to 18. This is due to some of our dependencies requiring a newer version of node. This is a breaking change for some folk! Also, 14 has been out of support for quite a while now and Node 18 gives us a full year. - [@​orta]

• Remove the user checks in GitHub comment/inline comment lookups, to allow using app tokens #1433 - [@​orta]
• Upgrade node engine from >=14.13.1 to >=18 [@​heltoft]
• Upgrade @types/node from ^10.11.3 to 18.19.18 [@​heltoft]
• GitLab: #1386 Move from @gitbeaker/node to @gitbeaker/rest [@​heltoft]
• GitLab: #1412 Danger fails to create inline comments on Gitlab [@​heltoft]
• GitLab: #1405 Can't post multiple inline comments [@​heltoft]
• GitLab: Do not delete system resolved danger inline comments [@​heltoft]
• Fix for ESM imports in Dangerfiles [@​mgol]

Commits

• e8e6baf Release 12.2.0
• 7ef1b6e Prettier fixes, and release notes
• f054550 Merge pull request #1440 from fabianehlert/feature/github-api-pagination
• 75438bc Merge pull request #1444 from kantivekariya/main
• 6b16212 feat: updated the json5 package
• bf158b8 GitHub: use files API with pagination
• faa3d5d Merge pull request #1439 from danger/logs_not_pr
• 686f401 CHANGELOG
• fb9f24a Logs when its not the PR run on GH workflows
• 05705c1 Release 12.1.0
• Additional commits viewable in compare view

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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @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)