chore(deps): update dependency danger to v13 #221
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:
4.0.1->13.0.5Release Notes
danger/danger-js (danger)
v13.0.5Compare Source
v13.0.4Compare Source
Fun sidenote, it's been exactly a year and we had to update the node version etc
v13.0.3Compare Source
v13.0.2Compare Source
v13.0.1Compare Source
v13.0.0Compare Source
@octokit/restfrom 18 to 20 to prevent transitive CVEs - Fixes #1479 [@fbartho]v12.3.4Compare Source
nullreturn fromloadOptionswhich occurs when a file is ignored.v12.3.3Compare Source
v12.3.2Compare Source
dangerfile.mts/dangerfile.mjs) [@matthewh]v12.3.1Compare Source
v12.3.0Compare Source
v12.2.1Compare Source
v12.2.0Compare Source
v12.1.0Compare Source
It's been 7 years since I looked at
danger initand err, the world of CI has changed quite a bit since then. So, Danger JS'sinitcommand now knows that GitHub Actions exists and will correctly offer some advice on how to set up a Dangerfile for it. - [@orta]v12.0.1Compare 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]
nodeengine from>=14.13.1to>=18[@heltoft]@types/nodefrom^10.11.3to18.19.18[@heltoft]@gitbeaker/nodeto@gitbeaker/rest[@heltoft]v12.0.0Compare 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]
nodeengine from>=14.13.1to>=18[@heltoft]@types/nodefrom^10.11.3to18.19.18[@heltoft]@gitbeaker/nodeto@gitbeaker/rest[@heltoft]v11.3.1Compare Source
pull_numberintothisPRin the GitHub SDL [@radimsv]DANGER_GHE_ACTIONS_BOT_USER_ID#1404 [@dimitar-hristov]v11.3.0Compare Source
@gitbeaker/nodefrom^21.3.0to^35.8.1[@buffcode]v11.2.8Compare Source
v11.2.7Compare Source
v11.2.6Compare Source
v11.2.5Compare Source
danger-pre.g.~/danger-projects#1375v11.2.4Compare Source
v11.2.3Compare Source
Turns on skipLibCheck so that an @types change doesn't break deploys to homebrew
v11.2.2Compare Source
Reverts a change for GitHub Actions which was likely causing duplicate comments #1337
v11.2.1Compare Source
v11.2.0Compare Source
danger.github.pr.draftfield to DSLv11.1.4Compare Source
a1d15db)9539b9d)c92a32e)184df2d)43c202b)a1af3e2)b5de611)v11.1.3Compare 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.2Compare Source
--stagingin Danger localv11.1.1Compare Source
v11.0.7Compare Source
ce16725)25dd589)88a6fe6)3eb82ab)852cd34)a49b939)v11.0.6Compare Source
b3a76c4)d99dfbd)5a48e1c)0b2c1d3)7f3c5ea)v11.0.5Compare Source
v11.0.4Compare Source
v11.0.2Compare 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.apipretty extensively in your Dangerfiles, but better to keep an eye out.v10.9.0Compare Source
34fe471)06928e3)fb66c81)6303c88)9049848)dc54972)0b5865f)ab77e3c)a7355a3)3411074)99e19f7)d896baf)4804f80)38a963e)68ab2e9)fb630ec)v10.8.0Compare Source
danger local --outputJSONfor #1177 [@orta]jsonpointerfor #1174 [@unfernandito]parse-link-headerfor CVE-2021-23490 #1190 [@fbartho]v10.7.1Compare Source
v10.7.0Compare Source
v10.6.6Compare Source
GitLabApitodanger.gitlab.api. - [@shyim]danger.gitlab.api.addLabelsanddanger.gitlab.api.removeLabels. - [@shyim]v10.6.4Compare Source
v10.6.3Compare Source
ciRunURLunderlying env var - [@rogerluan]v10.6.2Compare Source
gitlab.approvals- kelvin-lemonv10.6.1Compare Source
v10.6.0Compare Source
DANGER_DISABLE_TSCenvironment variable to disable transpiling with tsc, providing a way to force transpilingwith Babel - [@ozzieorca]
--newCommentand--removePreviousComments- [@davidhouweling]v10.5.4Compare Source
danger localnot passing through--staging- [@g3offrey]v10.5.3Compare Source
danger localnot showing commit messages - [@hmschreiner]v10.5.2Compare Source
danger.git.headanddanger.git.base- [@jamiebuilds]v10.5.1Compare Source
v10.5.0Compare Source
--use-github-checks#1073 [@wardpeet]v10.4.1Compare Source
tsconfig.jsonfile lookup strategy: it now looks for it starting from the location of the danger file.#1068 [@igorbek]
v10.4.0Compare Source
DANGER_FAKE_CIetc. [@orta]v10.3.1Compare Source
npx danger-ts[@orta]v10.3.0Compare Source
--ignoreOutOfDiffCommentsso that you can ignore inline-comments for lines that were not changedin the checked PR. The comments would be ignored completely - they won't even show in the results comment. [@pinkasey]
v10.2.1Compare Source
v10.2.0Compare Source
createOrUpdatePR, add the description (as done when editing) - [@sogame]v10.1.1Compare Source
27d1dcc)585b006)16d8666)0a33bfd)56d36bb)8090b86)bf3e021)dbac25a)f58ee85)94688fe)c17604e)4ab7345)e7d9b6a)4e36b7c)297a254)94475c3)d5c3172)v10.1.0Compare Source
createOrAddLabeluse pagination to fetch them all - [@sogame]v10.0.0Compare Source
Changed JSON patch implementation for better memory performance. [@dkundel]
Breaking:
JSONPatchForFilewill return a different order of operations than previously. It will also return apathwith the index of the element inserted into an array foraddoperations.v9.4.0Compare Source
24b0965)dcf1472)49b6f27)e6c7436)31a1961)v9.3.0Compare Source
danger localcommand - [@soyn]parse-difflibrary - [@417-72KI]@octokit/restdeprecation warning when using.issues.addLabels()- [@sogame]v9.2.10Compare Source
v9.2.9Compare Source
v9.2.8Compare Source
00d11ee)v9.2.7Compare Source
v9.2.6Compare Source
v9.2.5Compare Source
v9.2.4Compare Source
v9.2.3Compare Source
v9.2.2Compare Source
v9.2.1Compare Source
v9.2.0Compare Source
v9.1.8Compare Source
v9.1.7Compare Source
v9.1.5Compare Source
v9.1.4Compare Source
BITBUCKET_REPO_FULL_NAMEin bitbucket pipeline. - [@Soyn]v9.1.3Compare Source
v9.1.1Compare Source
v9.1.0Compare Source
v9.0.3Compare Source
handleResultsto be called without agitobject - [@jtreanor]v9.0.2Compare Source
v9.0.1Compare Source
v9.0.0Compare Source
v8.0.0Compare Source
v7.1.4Compare Source
danger.github.utils.createOrUpdatePR- [@ds300]v7.1.3Compare Source
v7.1.2Compare Source
Update ts-jest to 24.0.2 - [@friederbluemle]
Adds a fix for the default name of Danger in status - [@orta]
Adds
danger.git.fileMatch.getKeyedPaths(), providing more convenient access to paths. This replacesfileMatch.tap()andfileMatch.debug().This makes it much simpler to compose a collection of file checks - [@paulmelnikow]
v7.1.1Compare Source
b64b42a)v7.1.0Compare Source
Adds Chainsmoker, and expands the Danger DSL with the addition of
danger.git.fileMatch.This makes it much simpler to compose a collection of file checks - [@paulmelnikow]
v7.0.19Compare Source
v7.0.17Compare Source
v7.0.16Compare Source
v7.0.15Compare Source
v7.0.14Compare Source
linesOfCodeinGitDSL- [@ninjaprox]v7.0.13Compare Source
v7.0.12Compare Source
v7.0.11Compare Source
v7.0.10Compare Source
36de6b0)d096d18)v7.0.9Compare Source
v7.0.8Compare Source
v7.0.7Compare Source
vm2from Danger, it's not being used in Peril now - [@orta]danger prwith--jsonor --js` now don't require a Dangerfile to be present - [@orta]v7.0.4Compare Source
GITHUB_URLinstead of justDANGER_GITHUB_URLfor GitHub Enterprise. - [@Aghassi]v7.0.2Compare Source
(#804) - [@NMinhNguyen]
v5.0.0-beta-24. @dtinth
v7.0.1Compare Source
v7.0.0Compare Source
Updates
@octokit/restto v16.x.x - this is a major semver change on their end, which I know it breaks some ofArtsy/Danger's Peril Dangerfiles, so it's possible that it could break your Dangerfiles too. How do you know?
Roughly, if you have any code that uses
danger.github.apithen it's very possible that you need to update your code.There are update notes here, but if you're using TypeScript
then it'll raise the issues at a type-check level. Note, that this version may cause issues if you are using GitHub
Enterprise, you can get updates here.
v6.1.13Compare Source
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, 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.