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

[Snyk] Upgrade node-fetch from 2.6.7 to 2.6.8 #13

Closed
wants to merge 1 commit into from

Conversation

snyk-bot
Copy link

@snyk-bot snyk-bot commented Feb 3, 2023

Snyk has created this PR to upgrade node-fetch from 2.6.7 to 2.6.8.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


  • The recommended version is 1 version ahead of your current version.
  • The recommended version was released 22 days ago, on 2023-01-13.
Release notes
Package name: node-fetch from node-fetch GitHub release notes
Commit messages
Package name: node-fetch
  • 6e9464d ci(release): install dependencies
  • dd2a0ba ci(release): install dependencies
  • 49bef02 ci(release): use latest Node LTS
  • ce37bcd ci(semantic-release): config
  • 1768eaa ci(release): initial version
  • 8bb6e31 fix: prevent hoisting of the undefined `global` variable in `browser.js` (#1534)
  • e218f8d Add missing changelog entries. (#1613)
  • fddad0e fix(headers): don't forward secure headers on protocol change (#1605)
  • 50536d1 fix: premature close with chunked transfer encoding and for async iterators in Node 12 (#1172)
  • 838d971 Handle zero-length OK deflate responses (#903)

Compare


Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

🧐 View latest project report

🛠 Adjust upgrade PR settings

🔕 Ignore this dependency or unsubscribe from future upgrade PRs

@trhinehart-godaddy trhinehart-godaddy deleted the snyk-upgrade-e4eb9711388a02c4f0ac93f7b1fc0a5d branch July 27, 2023 21:43
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.

None yet

2 participants