Packages

@zeit/fetch

6.0.0 · 3 Mar 2020MIT56.9k / weekRepositoryHomepagenpmAtom feed

Upgrading @zeit/fetch From 2.0.2 to 6.0.0

16 releases in betweennotes for 4

Reading releases, release notes and advisories…

Other targets from 2.0.2Newest 2.x2.1.0
5.0.0, 3.0.0 have no release note on GitHub or in the repository's changelog, so their breaking changes are missing from the counts below.
  1. 2.0.2yours
  2. 4 releases
  3. 3.0.0major
  4. 6 releases
  5. 5.0.0major
  6. 3 releases
  7. 6.0.0target
1+
change to make
0
advisories fixed
?
new
4+
fixes

Counted from 4 of 16 release notes. Advisories are counted from the advisory database, in full.

Before you upgrade

Tick each one off as you go
  • Breaking6.0.0

Release by release

  1. 6.0.0

    Migration needed3 Mar 2020
    • Breaking

      Bump @zeit/fetch-retry to v5.0.0

  2. 5.2.0nothing new or fixed in the note

  3. 5.1.1

    3 Oct 20191 fix
    • Fixed

      Allow to pass agent options

  4. 3.0.3 – 5.1.06 releases, no release note

  5. 3.0.2

    30 Apr 20183 fixes
    • Fixed

      Update to latest @zeit/eslint-config-node and add editorconfig: abc437b7ee383087dba1d3349a3f8605f3c2068d

    • Fixed

      Fix lint: c210a2c8a69575a23f74ab1cb2a934d460204706, fdde59804b7d93c2d3983bb4ca499715516cc6b6

    • Fixed

      Don't invoke JSON.stringify() when the request body is a Buffer

  6. 2.0.3 – 3.0.16 releases, no release note

1 internal line (docs, tests, tooling) left out.

A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.