Packages

cacache

21.0.2 · 11 Nov 2026ISC44M / weekRepositoryHomepagenpmAtom feed

Upgrading cacache From 16.0.1 to 21.0.2

38 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 16.0.1Newest 16.x16.1.3
  1. 16.0.1yours
  2. 10 releases
  3. 17.0.0major
  4. 12 releases
  5. 18.0.0major
  6. 4 releases
  7. 19.0.0major
  8. 1 release
  9. 20.0.0major
  10. 4 releases
  11. 21.0.0major
  12. 1 release
  13. 21.0.2target

Before you upgrade

Tick each one off as you go
  • Breaking21.0.0
  • Breaking21.0.0
  • Breaking20.0.0
  • Breaking19.0.0
  • Breaking18.0.0
  • Breaking17.0.0
  • Breaking17.0.0
  • Breaking17.0.0
  • Breaking17.0.0

Release by release

  1. 21.0.2nothing new or fixed in the note

  2. 21.0.1

    9 Jun 20261 fix
    • Fixed

      Create cache directory tags

  3. 21.0.0

    Migration needed18 May 20261 new
    • Breaking

      cacache now supports node ^22.22.2 || ^24.15.0 || >=26.0.0

    • Breaking

      template-oss-apply

    • New

      Bump to new node engine range

  4. 20.0.1 – 20.0.44 releases, nothing new or fixed in the notes

  5. 20.0.0

    Migration needed24 Jul 20251 fix
    • Breaking

      cacache now supports node ^20.17.0 || >=22.9.0

    • Fixed

      Align to npm 11 node engine range

  6. 19.0.1nothing new or fixed in the note

  7. 19.0.0

    Migration needed26 Sep 20241 fix
    • Breaking

      cacache now supports node ^18.17.0 || >=20.5.0

    • Fixed

      Align to npm 10 node engine range

  8. 18.0.4

    11 Jul 20241 fix
    • Fixed

      Limit concurrent open files during lsstream

38 internal lines (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.