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 cross-fetch from 3.1.0 to 3.1.2 #1397

Merged
merged 1 commit into from
Apr 15, 2021

Conversation

snyk-bot
Copy link
Contributor

Snyk has created this PR to upgrade cross-fetch from 3.1.0 to 3.1.2.

merge advice
ℹ️ 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 2 versions ahead of your current version.
  • The recommended version was released a month ago, on 2021-03-19.
Release notes
Package name: cross-fetch
  • 3.1.2 - 2021-03-19

    🐞 added missing Headers interface augmentation from lib.dom.iterable.d.ts (#97)

  • 3.1.1 - 2021-03-18

    🐞 fixed missing fetch api types from constructor signatures #96 (thanks @ jstewmon)

  • 3.1.0 - 2021-03-13

    ⚡️ improved TypeScript support with own fetch API type definitions (thanks @ jstewmon)
    ⚡️ set fetch.ponyfill to true when custom ponyfill implementation is used.
    💡 set the same fetch API test suite to run against node-fetch, whatwg-fetch and native fetch.

from cross-fetch GitHub release notes
Commit messages
Package name: cross-fetch

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

@liangyuanruo liangyuanruo merged commit 3595424 into develop Apr 15, 2021
@liangyuanruo liangyuanruo deleted the snyk-upgrade-4b0ce78ec778a1a3fd189b893d17d9fc branch April 15, 2021 03:25
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.

2 participants