Skip to content

build(deps): Bump simple-git and @wordpress/env - #246

Merged
justlevine merged 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-7ca936124c
Nov 17, 2026
Merged

justlevine merged 1 commit into
mainfrom
dependabot/npm_and_yarn/multi-7ca936124c

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Bumps simple-git to 4.1.0 and updates ancestor dependency @wordpress/env. These dependencies need to be updated together.

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

Updates @wordpress/env from 11.17.0 to 12.1.0

Changelog

Sourced from @​wordpress/env's changelog.

12.1.0 (2026-11-04)

New Features

  • Add an experimental php runtime that serves WordPress with the installed PHP's built-in web server and a SQLite database, without Docker (#85512, #85574).

Bug Fixes

  • Point the bullseye-security apt sources of the bullseye-based WordPress images (PHP 7.3, 7.4, and 8.0) at archive.debian.org instead of dropping them, so the images keep receiving Debian security updates (#85469).

Internal

  • Update the Vitest development dependency to 5.0.5 (#86173).

12.0.0 (2026-10-20)

Breaking Changes

  • Raise the minimum required Node.js version to >=22.13.0, for stable require(esm) support (#84313).

Bug Fixes

  • Download the PHPUnit test library for a WordPress alpha, beta or RC version from its X.Y branch of WordPress/wordpress-develop when that branch exists, instead of always from trunk. A maintenance branch between point releases, such as 7.1.4-alpha, no longer gets trunk's tests, which can depend on code only trunk has. A release falls back to its X.Y branch when its tag does not exist yet. Cached test libraries now also update to the fetched version instead of staying on the first one downloaded (#84758).
Commits
  • 9b70363 chore(release): publish
  • 75eac8c Update changelog files
  • 3445af6 Merge changes published in the Gutenberg plugin "release/24.4" branch
  • 8d30f92 chore(release): publish
  • e7922b3 Update changelog files
  • e4d93b0 Merge changes published in the Gutenberg plugin "release/24.3" branch
  • fa4301b Update changelog files
  • 5c222d1 Merge changes published in the Gutenberg plugin "release/24.3" branch
  • 2555c8d Update changelog files
  • 558d1e6 Merge changes published in the Gutenberg plugin "release/24.3" branch
  • See full diff in compare view

Open WordPress Playground Preview

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 11, 2026
Bumps [simple-git](https://github.com/steveukx/git-js/tree/HEAD/simple-git) to 4.1.0 and updates ancestor dependency [@wordpress/env](https://github.com/WordPress/gutenberg/tree/HEAD/packages/env). These dependencies need to be updated together.


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)

Updates `@wordpress/env` from 11.17.0 to 12.1.0
- [Release notes](https://github.com/WordPress/gutenberg/releases)
- [Changelog](https://github.com/WordPress/gutenberg/blob/trunk/packages/env/CHANGELOG.md)
- [Commits](https://github.com/WordPress/gutenberg/commits/@wordpress/env@12.1.0/packages/env)

---
updated-dependencies:
- dependency-name: "@wordpress/env"
  dependency-version: 12.1.0
  dependency-type: direct:development
- dependency-name: simple-git
  dependency-version: 4.0.2
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/multi-7ca936124c branch from 91f1945 to 1b3359c Compare November 17, 2026 18:49
@justlevine
justlevine merged commit a22d2e6 into main Nov 17, 2026
14 checks passed
@justlevine
justlevine deleted the dependabot/npm_and_yarn/multi-7ca936124c branch November 17, 2026 18:56
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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant