Packages

@simple-git/argv-parser

3.0.0 · 16 Nov 2026MIT11.7M / weekRepositorynpmAtom feed

Upgrading @simple-git/argv-parser From 2.0.1 to 3.0.0

1 release 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.
  1. 2.0.1yours
  2. 3.0.0target
?
changes to make
0
advisories fixed
1
new
0
fixes

Security

  • Remove the vulnerabilityCheck export, use parseArgv(...tokens).vulnerabilities and parseEnv(env).vulnerabilities instead. Each vulnerability now also carries the configKey or envKey that triggered it.

    3.0.0
  • Closing the loop on any configuration setting ending with .cmd or command under the catch-all allowUnsafeCommandBinaries setting (only enforced with the new unsafe.recommended option, or strict), and blocking gpg.ssh.defaultKeyCommand under allowUnsafeGpgProgram.

    3.0.0
  • allowUnsafePager will now catch setting a custom binary in git grep --open-files-in-pager.

    3.0.0
  • allowUnsafePager now also covers interactive.diffFilter, the shell command that git add -p and the other --patch commands pipe their diff through.

    3.0.0
  • New (deprecated on arrival, prefer allowConfig) allowUnsafeSendEmailConfig option covering the sendemail.* keys that git send-email runs as commands, reads as files or uses to turn off certificate verification (sendmailCmd, toCmd, ccCmd, headerCmd, smtpServer, smtpServerOption, smtpSSLCertPath, smtpSSLClientCert, smtpSSLClientKey, aliasesFile and mailmap.file, including their per-identity sendemail.<identity>.* variants), and the imap.tunnel, imap.host and imap.sslVerify keys used by git imap-send.

    3.0.0
  • New (deprecated on arrival, prefer allowConfig) allowUnsafeWebServerConfig option covering the instaweb.httpd, instaweb.modulePath and instaweb.gitwebDir keys used by git instaweb.

    3.0.0
  • New (deprecated on arrival, prefer allowConfig) allowUnsafeBrowser option covering the browser.<tool>.path, browser.<tool>.cmd, man.<tool>.path and man.<tool>.cmd keys used by git help and git instaweb to open a browser or man page viewer. browser.<tool>.cmd and man.<tool>.cmd were previously covered by allowUnsafeCommandBinaries.

    3.0.0
  • New (deprecated on arrival, prefer allowConfig) allowUnsafeSignatureTrust option covering gpg.ssh.allowedSignersFile, gpg.ssh.revocationFile and gpg.minTrustLevel, which decide which signatures pass verification.

    3.0.0
  • allowUnsafePack now blocks --exec for every command other than rebase, as it names the remote program for push, send-pack, fetch-pack, archive --remote and ls-remote (previously only push).

    3.0.0
  • New allowUnsafeConfigRename option blocking git config --rename-section / git config rename-section, which could move keys written under a harmless section name (eg: foo.fsmonitor) into one that runs commands (core.fsmonitor).

    3.0.0

Release by release

  1. 3.0.0

    Security fix16 Nov 20261 new
    • Security

      Remove the vulnerabilityCheck export, use parseArgv(...tokens).vulnerabilities and parseEnv(env).vulnerabilities instead. Each vulnerability now also carries the configKey or envKey that triggered it.

    • Security

      Closing the loop on any configuration setting ending with .cmd or command under the catch-all allowUnsafeCommandBinaries setting (only enforced with the new unsafe.recommended option, or strict), and blocking gpg.ssh.defaultKeyCommand under allowUnsafeGpgProgram.

    • Security

      allowUnsafePager will now catch setting a custom binary in git grep --open-files-in-pager.

    • Security

      allowUnsafePager now also covers interactive.diffFilter, the shell command that git add -p and the other --patch commands pipe their diff through.

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.