simple-git
4.1.0 · 16 Nov 2026MIT15.5M / weekRepositorynpmAtom feed
Upgrading simple-git From 2.5.0 to 2.6.0
1 release in betweenevery note read
Reading releases, release notes and advisories…
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 0
- fixes
Security
8 advisories still affect 2.6.0
- Command injection in simple-githigh · GHSA-28xr-mwxg-3qc8
- Command injection in simple-githigh · GHSA-3f95-r44v-8mrg
- simple-git: unsafe-operations plugin bypass via git long-option abbreviation (--receive-p/--exe) -> command execution (residual of CVE-2026-28291)high · GHSA-858h-whjf-mvg5
Upgrading to 4.0.0 clears them.
7 other lines we could not sort, mostly version bumps
- 2.6.0
TL;DR -
.thenand.catchcan now be called on the standardsimpleGitchain to handle the promise returned by the most recently added task... essentially, promises now just work the way you would expect them to. - 2.6.0
The main export from
simple-gitno longer shows the deprecation notice for using the.thenfunction, it now exposes the promise chain generated from the most recently run task, allowing the combination of chain building and ad-hoc splitting off to a new promise chain. - 2.6.0
Promise / async interface and TypeScript types all available from the
simple-gitimport rather than needingsimple-git/promise, see examples in the ReadMe or in the consumer tests. - 2.6.0
Tasks that previously validated their usage and rejected with a
TypeErrorwill now reject with aTaskConfigurationError. - 2.6.0
Tasks that previously rejected with a custom object (currently only
git.mergewhen the auto-merge fails) will now reject with aGitResponseErrorwhere previously it was a modifiedError. - 2.6.0
git.clean(...)will now return aCleanSummaryinstead of the raw string data - 2.6.0
git.raw(...)now accepts any number of leading string arguments as an alternative to the single array of strings.
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.