Skip to content

chore(deps): bump @simple-git/argv-parser and simple-git - #290

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/multi-9ee64f1adb
Open

dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/multi-9ee64f1adb

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Oct 30, 2026 •

Copy link
Copy Markdown
Contributor

Bumps @simple-git/argv-parser to 3.0.0 and updates ancestor dependency simple-git. These dependencies need to be updated together.

Updates @simple-git/argv-parser from 1.1.1 to 3.0.0

Release notes

Sourced from @​simple-git/argv-parser's releases.

@​simple-git/argv-parser@​3.0.0

Major Changes

  • df13aeb: 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.

Minor Changes

  • df13aeb: Add the allowConfig and strict options. Configuration keys outside the built-in list of known-safe keys (SAFE_CONFIG_KEYS) and the keys named in allowConfig now emit a one-off SIMPLE_GIT_UNLISTED_CONFIG warning, or are rejected when strict: true is set. Known-unsafe keys can now be permitted individually through allowConfig, and environment variables through allowEnvironment, deprecating the unsafe.allowUnsafe* options that only covered configuration keys or environment variables (they continue to work as before).

  • a996f0f: Thanks to @​manus-pi and @​eliteaja11-dev for submitting CVE proposals that contributed to these changes.

    When the recommended checks are enabled (with unsafe.recommended: true or strict: true), HOME and XDG_CONFIG_HOME supplied through .env() with a value other than the one in process.env require allowUnsafeConfigPaths (or naming them in allowEnvironment), as git reads the global configuration from $HOME/.gitconfig and $XDG_CONFIG_HOME/git/config in the same way as GIT_CONFIG_GLOBAL. Passing the inherited value through is unaffected, and neither is removed from the inherited environment.

    parseEnv accepts the inherited environment as an optional second argument, used to compare HOME and XDG_CONFIG_HOME against.

    isGuardedEnvKey is now exported from @simple-git/argv-parser, identifying the environment variables (GIT_* and the others git reads, such as EDITOR and PAGER) that simple-git removes from an inherited environment.

  • c8ee6bb: Vulnerability reports:

    With thanks to @​manus-pi, @​manus-use, @​ba-am, @​mspiq, @​hoseinenddev, @​freyesperales, @​dalberrt, @​zer0d4y5, @​gamster01, @​humaneBicycle, @​Hama1cco, @​eliteaja11-dev, @​Cone-Tester, @​Figo5, @​MalwareEZ, @​zachariah-mithani, @​shaswata56, @​Akokonunes for submitting CVE proposals that contributed to these changes.

    • 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.
    • allowUnsafePager will now catch setting a custom binary in git grep --open-files-in-pager.
    • allowUnsafePager now also covers interactive.diffFilter, the shell command that git add -p and the other --patch commands pipe their diff through.
    • 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.
    • new (deprecated on arrival, prefer allowConfig) allowUnsafeWebServerConfig option covering the instaweb.httpd, instaweb.modulePath and instaweb.gitwebDir keys used by git instaweb.
    • 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.
    • new (deprecated on arrival, prefer allowConfig) allowUnsafeSignatureTrust option covering gpg.ssh.allowedSignersFile, gpg.ssh.revocationFile and gpg.minTrustLevel, which decide which signatures pass verification.
    • 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).
    • 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).
    • allowUnsafeExec now also covers the git filter-branch options that run a shell command: --setup, --env-filter, --tree-filter, --index-filter, --parent-filter, --msg-filter, --commit-filter and --tag-name-filter.
    • allowUnsafeDiffExternal now also covers difftool.<tool>.path, matching mergetool.<tool>.path under allowUnsafeMergeDriver.
  • df13aeb: Add templateArgv, isTemplateStringsArray, remoteUrl and refName for building a git argv from a tagged template literal, where every interpolated value is treated as untrusted data. simple-git uses these for git.cmd.

... (truncated)

Changelog

Sourced from @​simple-git/argv-parser's changelog.

3.0.0

Major Changes

  • df13aeb: 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.

Minor Changes

  • df13aeb: Add the allowConfig and strict options. Configuration keys outside the built-in list of known-safe keys (SAFE_CONFIG_KEYS) and the keys named in allowConfig now emit a one-off SIMPLE_GIT_UNLISTED_CONFIG warning, or are rejected when strict: true is set. Known-unsafe keys can now be permitted individually through allowConfig, and environment variables through allowEnvironment, deprecating the unsafe.allowUnsafe* options that only covered configuration keys or environment variables (they continue to work as before).

  • a996f0f: Thanks to @​manus-pi and @​eliteaja11-dev for submitting CVE proposals that contributed to these changes.

    When the recommended checks are enabled (with unsafe.recommended: true or strict: true), HOME and XDG_CONFIG_HOME supplied through .env() with a value other than the one in process.env require allowUnsafeConfigPaths (or naming them in allowEnvironment), as git reads the global configuration from $HOME/.gitconfig and $XDG_CONFIG_HOME/git/config in the same way as GIT_CONFIG_GLOBAL. Passing the inherited value through is unaffected, and neither is removed from the inherited environment.

    parseEnv accepts the inherited environment as an optional second argument, used to compare HOME and XDG_CONFIG_HOME against.

    isGuardedEnvKey is now exported from @simple-git/argv-parser, identifying the environment variables (GIT_* and the others git reads, such as EDITOR and PAGER) that simple-git removes from an inherited environment.

  • c8ee6bb: Vulnerability reports:

    With thanks to @​manus-pi, @​manus-use, @​ba-am, @​mspiq, @​hoseinenddev, @​freyesperales, @​dalberrt, @​zer0d4y5, @​gamster01, @​humaneBicycle, @​Hama1cco, @​eliteaja11-dev, @​Cone-Tester, @​Figo5, @​MalwareEZ, @​zachariah-mithani, @​shaswata56, @​Akokonunes for submitting CVE proposals that contributed to these changes.

    • 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.
    • allowUnsafePager will now catch setting a custom binary in git grep --open-files-in-pager.
    • allowUnsafePager now also covers interactive.diffFilter, the shell command that git add -p and the other --patch commands pipe their diff through.
    • 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.
    • new (deprecated on arrival, prefer allowConfig) allowUnsafeWebServerConfig option covering the instaweb.httpd, instaweb.modulePath and instaweb.gitwebDir keys used by git instaweb.
    • 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.
    • new (deprecated on arrival, prefer allowConfig) allowUnsafeSignatureTrust option covering gpg.ssh.allowedSignersFile, gpg.ssh.revocationFile and gpg.minTrustLevel, which decide which signatures pass verification.
    • 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).
    • 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).
    • allowUnsafeExec now also covers the git filter-branch options that run a shell command: --setup, --env-filter, --tree-filter, --index-filter, --parent-filter, --msg-filter, --commit-filter and --tag-name-filter.
    • allowUnsafeDiffExternal now also covers difftool.<tool>.path, matching mergetool.<tool>.path under allowUnsafeMergeDriver.
  • df13aeb: Add templateArgv, isTemplateStringsArray, remoteUrl and refName for building a git argv from a tagged

... (truncated)

Commits
  • 0b2e71b Version Packages
  • 86fadaa Rename strictConfig to strict to more closely match the purpose (#1215)
  • ddb5b6b Create unsafe.recommended to enable catch-all configuration detection. (#1213)
  • a996f0f Guard HOME and XDG_CONFIG_HOME supplied through .env() (#1209)
  • c8ee6bb Add tests for report rejections and resolve GHSA issues (#1206)
  • df13aeb Allow-list configuration keys, add git.cmd tagged templates and a security ...
  • f09081b Version Packages
  • 68874c2 Add VISUAL to tracked environment variables for allowUnsafeEditor (#1201)
  • 3971917 Version Packages
  • d762810 Fix/vulnerability rebase exec (#1198)
  • Additional commits viewable in compare view

Updates simple-git from 3.36.0 to 4.1.0

Release notes

Sourced from simple-git's releases.

simple-git@4.1.0

Minor Changes

  • df13aeb: Add the allowConfig and strict options. Configuration keys outside the built-in list of known-safe keys (SAFE_CONFIG_KEYS) and the keys named in allowConfig now emit a one-off SIMPLE_GIT_UNLISTED_CONFIG warning, or are rejected when strict: true is set. Known-unsafe keys can now be permitted individually through allowConfig, and environment variables through allowEnvironment, deprecating the unsafe.allowUnsafe* options that only covered configuration keys or environment variables (they continue to work as before).

  • 4137780: The custom binary (the first string of the binary option or git.customBinary()) may now contain spaces when it looks like a path to a file, for example C:\Program Files\Git\bin\git.exe. The value must include a path separator and no part of the path may start or end with a space. The prefix (the optional second string) remains limited to the existing restricted character set, as it is passed to the binary as its first argument.

  • df13aeb: Add git.cmd for running commands written as tagged template literals, where every interpolated value is treated as untrusted data that can't add options, set configuration keys or select a remote helper transport. Add the remoteUrl() and refName() value wrappers for stricter validation of interpolated values.

  • a996f0f: Thanks to @​manus-pi and @​eliteaja11-dev for submitting CVE proposals that contributed to these changes.

    When the recommended checks are enabled (with unsafe.recommended: true or strict: true), HOME and XDG_CONFIG_HOME supplied through .env() with a value other than the one in process.env require allowUnsafeConfigPaths (or naming them in allowEnvironment), as git reads the global configuration from $HOME/.gitconfig and $XDG_CONFIG_HOME/git/config in the same way as GIT_CONFIG_GLOBAL. Passing the inherited value through is unaffected, and neither is removed from the inherited environment.

    parseEnv accepts the inherited environment as an optional second argument, used to compare HOME and XDG_CONFIG_HOME against.

    isGuardedEnvKey is now exported from @simple-git/argv-parser, identifying the environment variables (GIT_* and the others git reads, such as EDITOR and PAGER) that simple-git removes from an inherited environment.

  • 86fadaa: Settle on the use of strict to refer to the simpleGit configuration setting to enable strict controls, applying to both Git impacting environment variables and writing to the Git config.

    Use of the strict mode also implies the use of unsafe.recommended

  • c8ee6bb: Vulnerability reports:

    With thanks to @​manus-pi, @​manus-use, @​ba-am, @​mspiq, @​hoseinenddev, @​freyesperales, @​dalberrt, @​zer0d4y5, @​gamster01, @​humaneBicycle, @​Hama1cco, @​eliteaja11-dev, @​Cone-Tester, @​Figo5, @​MalwareEZ, @​zachariah-mithani, @​shaswata56, @​Akokonunes for submitting CVE proposals that contributed to these changes.

    • 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.
    • allowUnsafePager will now catch setting a custom binary in git grep --open-files-in-pager.
    • allowUnsafePager now also covers interactive.diffFilter, the shell command that git add -p and the other --patch commands pipe their diff through.
    • 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.
    • new (deprecated on arrival, prefer allowConfig) allowUnsafeWebServerConfig option covering the instaweb.httpd, instaweb.modulePath and instaweb.gitwebDir keys used by git instaweb.
    • 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.
    • new (deprecated on arrival, prefer allowConfig) allowUnsafeSignatureTrust option covering gpg.ssh.allowedSignersFile, gpg.ssh.revocationFile and gpg.minTrustLevel, which decide which signatures pass verification.

... (truncated)

Changelog

Sourced from simple-git's changelog.

4.1.0

Minor Changes

  • df13aeb: Add the allowConfig and strict options. Configuration keys outside the built-in list of known-safe keys (SAFE_CONFIG_KEYS) and the keys named in allowConfig now emit a one-off SIMPLE_GIT_UNLISTED_CONFIG warning, or are rejected when strict: true is set. Known-unsafe keys can now be permitted individually through allowConfig, and environment variables through allowEnvironment, deprecating the unsafe.allowUnsafe* options that only covered configuration keys or environment variables (they continue to work as before).

  • 4137780: The custom binary (the first string of the binary option or git.customBinary()) may now contain spaces when it looks like a path to a file, for example C:\Program Files\Git\bin\git.exe. The value must include a path separator and no part of the path may start or end with a space. The prefix (the optional second string) remains limited to the existing restricted character set, as it is passed to the binary as its first argument.

  • df13aeb: Add git.cmd for running commands written as tagged template literals, where every interpolated value is treated as untrusted data that can't add options, set configuration keys or select a remote helper transport. Add the remoteUrl() and refName() value wrappers for stricter validation of interpolated values.

  • a996f0f: Thanks to @​manus-pi and @​eliteaja11-dev for submitting CVE proposals that contributed to these changes.

    When the recommended checks are enabled (with unsafe.recommended: true or strict: true), HOME and XDG_CONFIG_HOME supplied through .env() with a value other than the one in process.env require allowUnsafeConfigPaths (or naming them in allowEnvironment), as git reads the global configuration from $HOME/.gitconfig and $XDG_CONFIG_HOME/git/config in the same way as GIT_CONFIG_GLOBAL. Passing the inherited value through is unaffected, and neither is removed from the inherited environment.

    parseEnv accepts the inherited environment as an optional second argument, used to compare HOME and XDG_CONFIG_HOME against.

    isGuardedEnvKey is now exported from @simple-git/argv-parser, identifying the environment variables (GIT_* and the others git reads, such as EDITOR and PAGER) that simple-git removes from an inherited environment.

  • 86fadaa: Settle on the use of strict to refer to the simpleGit configuration setting to enable strict controls, applying to both Git impacting environment variables and writing to the Git config.

    Use of the strict mode also implies the use of unsafe.recommended

  • c8ee6bb: Vulnerability reports:

    With thanks to @​manus-pi, @​manus-use, @​ba-am, @​mspiq, @​hoseinenddev, @​freyesperales, @​dalberrt, @​zer0d4y5, @​gamster01, @​humaneBicycle, @​Hama1cco, @​eliteaja11-dev, @​Cone-Tester, @​Figo5, @​MalwareEZ, @​zachariah-mithani, @​shaswata56, @​Akokonunes for submitting CVE proposals that contributed to these changes.

    • 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.
    • allowUnsafePager will now catch setting a custom binary in git grep --open-files-in-pager.
    • allowUnsafePager now also covers interactive.diffFilter, the shell command that git add -p and the other --patch commands pipe their diff through.
    • 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.
    • new (deprecated on arrival, prefer allowConfig) allowUnsafeWebServerConfig option covering the instaweb.httpd, instaweb.modulePath and instaweb.gitwebDir keys used by git instaweb.
    • 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.

... (truncated)

Commits
  • 0b2e71b Version Packages
  • 86fadaa Rename strictConfig to strict to more closely match the purpose (#1215)
  • 497ecd1 Update recommended settings documentation (#1214)
  • ddb5b6b Create unsafe.recommended to enable catch-all configuration detection. (#1213)
  • 4137780 Allow spaces in custom binary paths, keep the prefix restricted (#1212)
  • a996f0f Guard HOME and XDG_CONFIG_HOME supplied through .env() (#1209)
  • c8ee6bb Add tests for report rejections and resolve GHSA issues (#1206)
  • df13aeb Allow-list configuration keys, add git.cmd tagged templates and a security ...
  • f09081b Version Packages
  • 68874c2 Add VISUAL to tracked environment variables for allowUnsafeEditor (#1201)
  • Additional commits viewable in compare view

@dependabot dependabot Bot added dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code labels Oct 30, 2026
Bumps [@simple-git/argv-parser](https://github.com/steveukx/git-js/tree/HEAD/packages/argv-parser) to 3.0.0 and updates ancestor dependency [simple-git](https://github.com/steveukx/git-js/tree/HEAD/simple-git). These dependencies need to be updated together.


Updates `@simple-git/argv-parser` from 1.1.1 to 3.0.0
- [Release notes](https://github.com/steveukx/git-js/releases)
- [Changelog](https://github.com/steveukx/git-js/blob/main/packages/argv-parser/CHANGELOG.md)
- [Commits](https://github.com/steveukx/git-js/commits/@simple-git/argv-parser@3.0.0/packages/argv-parser)

Updates `simple-git` from 3.36.0 to 4.1.0
- [Release notes](https://github.com/steveukx/git-js/releases)
- [Changelog](https://github.com/steveukx/git-js/blob/main/simple-git/CHANGELOG.md)
- [Commits](https://github.com/steveukx/git-js/commits/simple-git@4.1.0/simple-git)

---
updated-dependencies:
- dependency-name: "@simple-git/argv-parser"
  dependency-version: 2.0.1
  dependency-type: indirect
- dependency-name: simple-git
  dependency-version: 4.0.2
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-9ee64f1adb branch from 8ef06da to 42c9f35 Compare November 19, 2026 08:30
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file javascript Pull requests that update javascript code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants