Packages

simple-git

4.1.0 · 16 Nov 2026MIT15.5M / weekRepositorynpmAtom feed

Upgrading simple-git From 3.35.1 to 4.0.1

4 releases in betweenevery note read

Reading releases, release notes and advisories…

Other targets from 3.35.1Newest 3.x3.36.0Latest4.1.0
  1. 3.35.1yours
  2. 3.35.2
  3. 3.36.0security
  4. 4.0.0major
  5. 4.0.1target

Before you upgrade

Tick each one off as you go
  • Breaking4.0.0
  • Breaking4.0.0

Security

  • Note - ParsedVulnerabilities from argv-parser is removed in favour of a readonly array of Vulnerability to match usage in simple-git, rolled into the new vulnerabilityCheck for simpler access to the identified issues.

    3.36.0

Release by release

  1. 4.0.1

    25 Sep 20261 fix
    • Fixed

      Prepare package.json before publishing.

  2. 4.0.0

    Migration needed25 Sep 20262 new · 1 fix
    • Breaking

      Removed previously available default export, now uses a consistently named simpleGit export.

    • Breaking

      Removed legacy gitP export (change to using the main simpleGit export).

    • New

      Support one-shot stdin via git.input(data) (string or Buffer).

    • New

      Add allowUnsafeExec detection to rebase -x and rebase --exec.

    • Fixed

      Parse binary rename entries without byte counts in diff summaries.

  3. 3.36.0

    Security fix12 Apr 20261 new · 1 fix
    • Security

      Note - ParsedVulnerabilities from argv-parser is removed in favour of a readonly array of Vulnerability to match usage in simple-git, rolled into the new vulnerabilityCheck for simpler access to the identified issues.

    • New

      Extend known exploitable configuration keys and per-task environment variables.

    • Fixed

      Remove conflicting node:buffer import

  4. 3.35.2

    6 Apr 20261 fix
    • Fixed

      Improvements for mono-repo publishing pipeline

1 other line we could not sort, mostly version bumps
  • Removed previously deprecated import simple-git/promise (change to using the main simple-git import).

    4.0.0

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