chore(deps): update dependency danger to v12 #664
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
11.3.1
->12.3.3
Release Notes
danger/danger-js (danger)
v12.3.3
Compare Source
v12.3.2
Compare Source
dangerfile.mts
/dangerfile.mjs
) [@matthewh]v12.3.1
Compare Source
v12.3.0
Compare Source
v12.2.1
Compare Source
v12.2.0
Compare Source
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'sinit
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]
node
engine from>=14.13.1
to>=18
[@heltoft]@types/node
from^10.11.3
to18.19.18
[@heltoft]@gitbeaker/node
to@gitbeaker/rest
[@heltoft]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]
node
engine from>=14.13.1
to>=18
[@heltoft]@types/node
from^10.11.3
to18.19.18
[@heltoft]@gitbeaker/node
to@gitbeaker/rest
[@heltoft]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.
This PR was generated by Mend Renovate. View the repository job log.