Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

build(deps-dev): bump danger from 11.1.1 to 12.3.1 #456

Closed
wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jun 10, 2024

Bumps danger from 11.1.1 to 12.3.1.

Release notes

Sourced from danger's releases.

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

Release 11.3.1

No release notes provided.

... (truncated)

Changelog

Sourced from danger's changelog.

12.3.1

  • Fixes for created, modified ,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 [@​heltoft]
  • 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

  • GitLab: Upgrade @gitbeaker/node from ^21.3.0 to ^35.8.1 [@​buffcode]

11.2.8

11.2.7

... (truncated)

Commits
  • fff9545 Release 12.3.1
  • 465054e CHANGELOG
  • ef0d432 Merge pull request #1453 from sayali10/danger-log-for-pull_request_target
  • 0d3588e chore: update not PR condition for GH workflow
  • 810b9ca Merge pull request #1452 from koji-1009/fix/format
  • d5af2ef Merge pull request #1451 from szweier/fix-file-status
  • 8e17920 chore: Fix formatting of environment variable example
  • 7b7d74b Fix getPullRequestDiff test
  • 6883bcf Add and use status on GitHubFile
  • bb0f4c2 Release 12.3.0
  • Additional commits viewable in compare view

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 <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)

Bumps [danger](https://github.com/danger/danger-js) from 11.1.1 to 12.3.1.
- [Release notes](https://github.com/danger/danger-js/releases)
- [Changelog](https://github.com/danger/danger-js/blob/main/CHANGELOG.md)
- [Commits](danger/danger-js@11.1.1...12.3.1)

---
updated-dependencies:
- dependency-name: danger
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jun 10, 2024
Copy link
Contributor Author

dependabot bot commented on behalf of github Jun 24, 2024

Superseded by #460.

@dependabot dependabot bot closed this Jun 24, 2024
@dependabot dependabot bot deleted the dependabot/npm_and_yarn/danger-12.3.1 branch June 24, 2024 01:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants