Bump node-fetch and danger#7
Open
dependabot[bot] wants to merge 1 commit intomainfrom
Open
Conversation
Bumps [node-fetch](https://github.com/node-fetch/node-fetch) and [danger](https://github.com/danger/danger-js). These dependencies needed to be updated together. Updates `node-fetch` from 2.6.1 to 2.6.9 - [Release notes](https://github.com/node-fetch/node-fetch/releases) - [Commits](node-fetch/node-fetch@v2.6.1...v2.6.9) Updates `danger` from 10.6.6 to 10.9.0 - [Release notes](https://github.com/danger/danger-js/releases) - [Changelog](https://github.com/danger/danger-js/blob/main/CHANGELOG.md) - [Commits](danger/danger-js@10.6.6...10.9.0) --- updated-dependencies: - dependency-name: node-fetch dependency-type: indirect - dependency-name: danger dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Bumps node-fetch and danger. These dependencies needed to be updated together.
Updates
node-fetchfrom 2.6.1 to 2.6.9Release notes
Sourced from node-fetch's releases.
Commits
70f592dfix: "global is not defined" (#1704)0f1ebb0Prevent error when response is null (#1699)6e9464dci(release): install dependenciesdd2a0baci(release): install dependencies49bef02ci(release): use latest Node LTSce37bcdci(semantic-release): config1768eaaci(release): initial version8bb6e31fix: prevent hoisting of the undefinedglobalvariable inbrowser.js(#1534)e218f8dAdd missing changelog entries. (#1613)fddad0efix(headers): don't forward secure headers on protocol change (#1605)Maintainer changes
This version was pushed to npm by node-fetch-bot, a new releaser for node-fetch since your current version.
Updates
dangerfrom 10.6.6 to 10.9.0Release notes
Sourced from danger's releases.
... (truncated)
Changelog
Sourced from danger's changelog.
... (truncated)
Commits
202d727Release 10.9.034fe471Prepare for release06928e3Merge branch 'adjust-structured-diff-return-value' into mainfb66c81Merge pull request #1201 from berlysia/adjust-structured-diff-return-value6303c88Lock node-fetch to the latest 2.x9049848Merge pull request #1198 from jonny133/jonny133-node-fetch-2_6_7dc54972now structuredDiffForFile is well-typed0b5865fmake structuredDiffForFile for BitBucketServer the same as the othersab77e3cResolve node-fetch to 2.6.7a7355a3Merge pull request #1197 from danger/fb/fix-moved-json-crashDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)You can disable automated security fix PRs for this repo from the Security Alerts page.