Packages

giget

3.3.1 · 24 Jul 2026MIT44.1M / weekRepositoryHomepagenpmAtom feed

Upgrading giget From 2.0.0 to 3.3.1

7 releases in betweenevery note read

Reading releases, release notes and advisories…

The note of 3.0.0 lists no breaking change or deprecation, which is rare for a major.
?
changes to make
0
advisories fixed
6
new
3
fixes

Security

  • 🛡️ Bundled tar version updated to v7 with latest security fixes.

    3.0.0

Release by release

  1. 3.3.1nothing new or fixed in the note

  2. 3.3.0

    11 Jun 20262 new
    • New

      Support ignore

    • New

      Updated bundled dependencies (citty, npm, tar)

  3. 3.2.0

    26 Mar 20261 new · 3 fixes
    • New

      git: provider with sparse cloning support

    • Fixed

      _utils: Move hyphens to start of character classes in parseGitURI regex

    • Fixed

      cli: Prevent duplicate error messages

    • Fixed

      gitlab: Support subgroups and :: subdir delimiter

  4. 3.1.1 – 3.1.22 releases, nothing new or fixed in the notes

  5. 3.1.0

    21 Jan 20263 new
    • New

      Allow passing install options to nypm

    • New

      Lazy load nypm

    • New

      Lazy import tar

  6. 3.0.0

    Security fix20 Jan 2026
    • Security

      🛡️ Bundled tar version updated to v7 with latest security fixes.

1 other line we could not sort, mostly version bumps
  • Update deps

    3.1.2

2 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.