Skip to content
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

Bump node-fetch and next #33

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Oct 19, 2022

Bumps node-fetch to 2.6.7 and updates ancestor dependency next. These dependencies need to be updated together.

Updates node-fetch from 2.6.1 to 2.6.7

Release notes

Sourced from node-fetch's releases.

v2.6.7

Security patch release

Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.6...v2.6.7

v2.6.6

What's Changed

Full Changelog: node-fetch/node-fetch@v2.6.5...v2.6.6

v2.6.2

fixed main path in package.json

Commits
  • 1ef4b56 backport of #1449 (#1453)
  • 8fe5c4e 2.x: Specify encoding as an optional peer dependency in package.json (#1310)
  • f56b0c6 fix(URL): prefer built in URL version when available and fallback to whatwg (...
  • b5417ae fix: import whatwg-url in a way compatible with ESM Node (#1303)
  • 18193c5 fix v2.6.3 that did not sending query params (#1301)
  • ace7536 fix: properly encode url with unicode characters (#1291)
  • 152214c Fix(package.json): Corrected main file path in package.json (#1274)
  • See full diff in compare view
Maintainer changes

This version was pushed to npm by endless, a new releaser for node-fetch since your current version.


Updates next from 11.0.1 to 11.1.4

Release notes

Sourced from next's releases.

v12.3.2.-canary.11

Core Changes

  • Fix bundling and module resolution in the server layer: #40818
  • Handle loading returning undefined: #40938
  • Fix SWC loader ignore for the server layer when Babel is used: #40939
  • Code refactoring for webpack-config: #40942
  • Merge e2e test node_modules: #40926
  • Rename 404 -> not-found for new router: #40941
  • remove reducer from server bundle: #40959
  • [edge] serialize custom config to middleware-manifest: #40881
  • Font loader support in app: #40898
  • docs: add inline documentation for Link props: #40855
  • feat(experimental): option to polyfill fetch using undici in Node.js <18: #40318
  • Update return shape of generateStaticParams: #40965
  • remove legacy transform code: #40966
  • Revert "edge-ssr: bundle next/dist as ESM for better tree-shaking (#40251): #40967

Documentation Changes

  • Typo in middleware upgrade guide: #40963
  • Add useState and useEffect import: #40944

Misc Changes

  • Always show node_modules inside test in VS Code: #40956
  • misc: add benchmarking script for edge rendering: #40716
  • Add timeout to playwright setup job: #40960
  • Increase playwright install timeout to 5 min
  • Increase other timeouts

Credits

Huge thanks to @​shuding, @​timneutkens, @​feedthejim, @​ijjk, @​Schniz, @​hanneslund, @​HaNdTriX, @​sedlukha, @​hashlash, and @​Ethan-Arrowood for helping!

Commits
Maintainer changes

This version was pushed to npm by vercel-release-bot, a new releaser for next 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 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

You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [node-fetch](https://github.com/node-fetch/node-fetch) to 2.6.7 and updates ancestor dependency [next](https://github.com/vercel/next.js). These dependencies need to be updated together.


Updates `node-fetch` from 2.6.1 to 2.6.7
- [Release notes](https://github.com/node-fetch/node-fetch/releases)
- [Commits](node-fetch/node-fetch@v2.6.1...v2.6.7)

Updates `next` from 11.0.1 to 11.1.4
- [Release notes](https://github.com/vercel/next.js/releases)
- [Changelog](https://github.com/vercel/next.js/blob/canary/release.js)
- [Commits](vercel/next.js@v11.0.1...v11.1.4)

---
updated-dependencies:
- dependency-name: node-fetch
  dependency-type: indirect
- dependency-name: next
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@vercel
Copy link

vercel bot commented Oct 19, 2022

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Updated
safePostcode ❌ Failed (Inspect) Oct 19, 2022 at 10:04AM (UTC)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants