Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9
build(deps): [security] bump node-fetch from 2.6.0 to 2.6.1#56
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Open
dependabot-preview wants to merge1 commit intomasterChoose a base branch fromdependabot/npm_and_yarn/node-fetch-2.6.1
base:master
Could not load branches
Branch not found:{{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated.
Uh oh!
There was an error while loading.Please reload this page.
Conversation
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
Bumps [node-fetch](https://github.com/bitinn/node-fetch) from 2.6.0 to 2.6.1. **This update includes a security fix.**- [Release notes](https://github.com/bitinn/node-fetch/releases)- [Changelog](https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md)- [Commits](node-fetch/node-fetch@v2.6.0...v2.6.1)Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment
Labels
dependenciesPull requests that update a dependency file securityPull requests that address a security vulnerability
0 participants
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.
Uh oh!
There was an error while loading.Please reload this page.
This pull request was created by Dependabot Preview, and you've upgraded to Dependabot. This means it won't respond to
dependabot
commands nor will it be automatically closed if a new version is found.If you close this pull request, Dependabot will re-create it the next time it checks for updates and everything will work as expected.
Bumpsnode-fetch from 2.6.0 to 2.6.1.This update includes a security fix.
Vulnerabilities fixed
Sourced fromThe GitHub Security Advisory Database.
Release notes
Sourced fromnode-fetch's releases.
Changelog
Sourced fromnode-fetch's changelog.
Commits
b5e2e41
update version number2358a6c
Honor thesize
option after following a redirect and revert data uri support8c197f8
docs: Fix typos and grammatical errors in README.md (#686)1e99050
fix: Change error message thrown with redirect mode set to error (#653)244e6f6
docs: Show backers in README6a5d192
fix: Properly parse meta tag when parameters are reversed (#682)47a24a0
chore: Add opencollective badge7b13662
chore: Add funding link5535c2e
fix: Check for global.fetch before binding it (#674)1d5778a
docs: Add Discord badgeMaintainer changes
This version was pushed to npm byakepinski, a new releaser for node-fetch since your current version.
Dependabot 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 willnot automatically merge this PR because it includes a security patch update to a production dependency.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebase
will rebase this PR@dependabot recreate
will recreate this PR, overwriting any edits that have been made to it@dependabot merge
will merge this PR after your CI passes on it@dependabot squash and merge
will squash and merge this PR after your CI passes on it@dependabot cancel merge
will cancel a previously requested merge and block automerging@dependabot reopen
will reopen this PR if it is closed@dependabot close
will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot ignore this major version
will 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 version
will 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 dependency
will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)@dependabot use these labels
will set the current labels as the default for future PRs for this repo and language@dependabot use these reviewers
will set the current reviewers as the default for future PRs for this repo and language@dependabot use these assignees
will set the current assignees as the default for future PRs for this repo and language@dependabot use this milestone
will set the current milestone as the default for future PRs for this repo and language@dependabot badge me
will comment on this PR with code to add a "Dependabot enabled" badge to your readmeAdditionally, you can set the following in your Dependabotdashboard: