chore(deps): update dependency danger to v12 #883
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:
10.7.1
->12.3.0
Release Notes
danger/danger-js (danger)
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]v11.3.1
Compare Source
pull_number
intothisPR
in the GitHub SDL [@radimsv]DANGER_GHE_ACTIONS_BOT_USER_ID
#1404 [@dimitar-hristov]v11.3.0
Compare Source
@gitbeaker/node
from^21.3.0
to^35.8.1
[@buffcode]v11.2.8
Compare Source
v11.2.7
Compare Source
v11.2.6
Compare Source
v11.2.5
Compare Source
danger-pr
e.g.~/danger-projects
#1375v11.2.4
Compare Source
v11.2.3
Compare Source
Turns on skipLibCheck so that an @types change doesn't break deploys to homebrew
v11.2.2
Compare Source
Reverts a change for GitHub Actions which was likely causing duplicate comments #1337
v11.2.1
Compare Source
v11.2.0
Compare Source
danger.github.pr.draft
field to DSLv11.1.4
Compare Source
a1d15db
)9539b9d
)c92a32e
)184df2d
)43c202b
)a1af3e2
)b5de611
)v11.1.3
Compare Source
8e58eae
)f6d17c0
)4c52740
)6a216a1
)f5eeee0
)6a70f47
)ba84b5f
)15c00e0
)3367329
)47d2085
)dafdb02
)67737e8
)c0d8430
)89987a2
)27414d9
)507cb11
)ad51f2b
)a258814
)6c49cfe
)7a50540
)b427e3e
)116a3a4
)8dd9fd8
)d015c09
)b37c807
)v11.1.2
Compare Source
--staging
in Danger localv11.1.1
Compare Source
v11.0.7
Compare Source
ce16725
)25dd589
)88a6fe6
)3eb82ab
)852cd34
)a49b939
)v11.0.6
Compare Source
b3a76c4
)d99dfbd
)5a48e1c
)0b2c1d3
)7f3c5ea
)v11.0.5
Compare Source
v11.0.4
Compare Source
v11.0.2
Compare Source
Breaking: Upgrade @octokit/rest from ^16.43.1 to ^18.12.0 - #1204 [@fbartho]
This is only likely to hit you if you use
danger.github.api
pretty extensively in your Dangerfiles, but better to keep an eye out.v10.9.0
Compare Source
34fe471
)06928e3
)fb66c81
)6303c88
)9049848
)dc54972
)0b5865f
)ab77e3c
)a7355a3
)3411074
)99e19f7
)d896baf
)4804f80
)38a963e
)68ab2e9
)fb630ec
)v10.8.0
Compare Source
danger local --outputJSON
for #1177 [@orta]jsonpointer
for #1174 [@unfernandito]parse-link-header
for CVE-2021-23490 #1190 [@fbartho]Configuration
📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ 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 has been generated by Mend Renovate. View repository job log here.