Bump cross-fetch from 3.0.6 to 3.1.8
Bumps cross-fetch from 3.0.6 to 3.1.8.
Release notes
Sourced from cross-fetch's releases.
v3.1.8
What's Changed
- Restored caret range to node-fetch version for automatic feature and fix updates.
Full Changelog: https://github.com/lquixada/cross-fetch/compare/v3.1.7...v3.1.8
v3.1.7
What's Changed
- Updated node-fetch version to 2.6.12
Full Changelog: https://github.com/lquixada/cross-fetch/compare/v3.1.6...v3.1.7
v3.1.6
What's Changed
- Updated node-fetch version to 2.6.11
- Added caret range to node-fetch version for automatic feature and fix updates.
Full Changelog: https://github.com/lquixada/cross-fetch/compare/v3.1.5...v3.1.6
v3.1.5
What's Changed
- chore: updated node-fetch version to 2.6.7 by
@dlafrenierein lquixada/cross-fetch#124New Contributors
@dlafrenieremade their first contribution in lquixada/cross-fetch#124Full Changelog: https://github.com/lquixada/cross-fetch/compare/v3.1.4...v3.1.5
v3.1.4
🐞 fixed typescript errors.
v3.1.3
🐞 fixed typescript compilation error causing #95, #101, #102.
v3.1.2
🐞 added missing Headers interface augmentation from lib.dom.iterable.d.ts (#97)
v3.1.1
🐞 fixed missing fetch api types from constructor signatures #96 (thanks
@jstewmon)v3.1.0
⚡️ improved TypeScript support with own fetch API type definitions (thanks
@jstewmon) ⚡️ setfetch.ponyfilltotruewhen custom ponyfill implementation is used. 💡 set the same fetch API test suite to run againstnode-fetch,whatwg-fetchand native fetch.
Changelog
Sourced from cross-fetch's changelog.
3.1.8 (2023-07-02)
Bug Fixes
- restored caret on node-fetch version (6669927)
3.1.7 (2023-07-01)
3.1.6 (2023-05-14)
Features
Bug Fixes
- fixed ESTree.StaticBlock error (a66f21b)
Commits
0922089chore(release): 3.1.86669927fix: restored caret on node-fetch versionff14bddchore: improved release scriptd625e0dchore: release workflow now uses .nvmrc098ed1echore: improved release workflowcc2663bchore(release): 3.1.77c1fddechore: updated node-fetch to 2.6.12e298dbbchore: reordered if statement81049e1chore: removed github publish pipelinea80be7cchore: removed console log from specs- Additional commits viewable in compare view
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 rebasewill rebase this PR -
@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it -
@dependabot mergewill merge this PR after your CI passes on it -
@dependabot squash and mergewill squash and merge this PR after your CI passes on it -
@dependabot cancel mergewill cancel a previously requested merge and block automerging -
@dependabot reopenwill reopen this PR if it is closed -
@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually -
@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency -
@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the Security Alerts page.