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

fix: chore update dependency danger to v12 #67

Merged
merged 1 commit into from
Apr 18, 2024
Merged

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 16, 2024

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
danger ^11.3.1 -> ^12.0.0 age adoption passing confidence

Release Notes

danger/danger-js (danger)

v12.1.0

Compare Source

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]

v12.0.1

Compare Source

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]

v12.0.0

Compare Source

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]

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot requested review from a team, octosa-kitabisa, ugi-kitabisa and famrullah11 and removed request for a team April 16, 2024 11:04
@renovate renovate bot force-pushed the renovate/danger-12.x branch 8 times, most recently from fc96624 to 3679104 Compare April 17, 2024 07:31
@adeherysh adeherysh changed the title chore(deps): update dependency danger to v12 fix: chore update dependency danger to v12 Apr 18, 2024
@adeherysh adeherysh marked this pull request as ready for review April 18, 2024 05:17
@adeherysh adeherysh self-requested a review as a code owner April 18, 2024 05:17
@adeherysh adeherysh merged commit 86dcf1f into main Apr 18, 2024
4 checks passed
@adeherysh adeherysh deleted the renovate/danger-12.x branch April 18, 2024 05:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants