search

boostxyz / boost-protocol

A permissionless, trustless, and decentralized growth engine for protocol and application developers. It enables developers to bootstrap their projects by leveraging the power of community and the network effect.
https://boost-protocol.vercel.app
GNU General Public License v3.0
4 stars 2 forks source link

build(deps): bump danger/danger-js from 9.1.8 to 12.3.3 #148

Closed dependabot[bot] closed 1 week ago

dependabot[bot] commented 1 week ago

Bumps danger/danger-js from 9.1.8 to 12.3.3.

Release notes

Sourced from danger/danger-js's releases.

Release 12.3.3

No release notes provided.

Release 12.3.2

No release notes provided.

Release 12.3.1

No release notes provided.

Release 12.3.0

No release notes provided.

Release 12.2.1

No release notes provided.

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]

... (truncated)

Changelog

Sourced from danger/danger-js's changelog.

12.3.3

  • #1180 Set module properly when tsconfig does not contain compilerOptions.module [@​matthewh]

12.3.2

  • #1180 Adds support for ESM Dangerfiles (by using dangerfile.mts/dangerfile.mjs) [@​matthewh]

12.3.1

  • Fixes for created, modified and deleted files in GitHub - [@​szweier]
  • Dont log about github.pr not being available in pull_request_target - [@​sayali10]

12.3.0

  • Dockerfile changes - [@​glensc]
  • Use node 18 for pre-built versions of danger (used by Danger Swift / Kotlin et al) - [@​heltoft]

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 [@​heltyarnoft]
  • GitLab: Do not delete system resolved danger inline comments [@​heltoft]
  • Fix for ESM imports in Dangerfiles [@​mgol]

11.3.1

  • Adds pull_number into thisPR in the GitHub SDL [@​radimsv]
  • Clear missing DSL timeout when DSL is found so danger runner can exit faster when done [@​normano64]
  • Customise GHE actions bot user ID via DANGER_GHE_ACTIONS_BOT_USER_ID #1404 [@​dimitar-hristov]

11.3.0

... (truncated)

Commits


Dependabot compatibility score

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 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)
dependabot[bot] commented 1 week ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.