-
Notifications
You must be signed in to change notification settings - Fork 31
Bump node-fetch from 2.6.7 to 3.3.2 #730
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Unit Tests and CoverageShow Output
-----------------------|---------|----------|---------|---------|-------------------
|
ccada14
to
97d8427
Compare
Unit Tests and CoverageShow Output
-----------------------|---------|----------|---------|---------|-------------------
|
@dependabot rebase |
Bumps [node-fetch](https://github.com/node-fetch/node-fetch) from 2.6.7 to 3.3.2. - [Release notes](https://github.com/node-fetch/node-fetch/releases) - [Commits](node-fetch/node-fetch@v2.6.7...v3.3.2) --- updated-dependencies: - dependency-name: node-fetch dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <[email protected]>
97d8427
to
f36b6f6
Compare
Unit Tests and CoverageShow Output
-----------------------|---------|----------|---------|---------|-------------------
|
What's the ETA on this? Next.js 15 uses node-fetch 3, and trying to use this library with it is a bit of a pain, so we moved our company's web app to just hit the Vultr APIs directly without this lib. |
Bumps node-fetch from 2.6.7 to 3.3.2.
Release notes
Sourced from node-fetch's releases.
... (truncated)
Commits
8b3320d
fix: Remove the default connection close header. (#1736)7b86e94
fix: release "Allow URL class object as an argument for fetch()" #1696 (#1716)8ced5b9
docs: readme - non ESM example (#1707)71e376b
ci(release): use latest Node LTS (#1697)e093030
Allow URL class object as an argument for fetch() (#1696)55a4870
feat: add static Response.json (#1670)c071406
(1138) - Fixed HTTPResponseError with correct constructor and usage (#1666)6f72caa
docs: fix missing comma in example (#1623)2880238
fix: ReDoS referrer (#1611)e87b093
fix(Headers): don't forward secure headers on protocol change (#1599)Maintainer changes
This version was pushed to npm by node-fetch-bot, a new releaser for node-fetch since your current version.
You can trigger a rebase of this PR by commenting
@dependabot rebase
.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)