Skip to content

chore(deps): update all non-major dependencies - #797

Merged
renovate[bot] merged 1 commit into
masterfrom
renovate/all-minor-patch
Nov 18, 2026
Merged

renovate[bot] merged 1 commit into
masterfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Nov 17, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
@typescript-eslint/parser (source) 8.72.2 → 8.73.0 age confidence
simple-git (source) 4.0.2 → 4.1.0 age confidence
typescript-eslint (source) 8.72.2 → 8.73.0 age confidence

Release Notes

typescript-eslint/typescript-eslint (@​typescript-eslint/parser)

v8.73.0

Compare Source

This was a version bump only for parser to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.

steveukx/git-js (simple-git)

v4.1.0

Compare Source

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.
    • 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.
  • ddb5b6b: Add the unsafe.recommended option, enabling the checks that use broader catch-all rules (such as any configuration
    key ending in .cmd or command under allowUnsafeCommandBinaries). Defaults to false, and is implied by
    strict: true. It will default to true in the next major version.

    Each Vulnerability reported by @simple-git/argv-parser now carries a level of default for explicitly
    identified risks, or recommended for those caught by a catch-all rule. The VulnerabilityLevel type is exported.

Patch Changes
typescript-eslint/typescript-eslint (typescript-eslint)

v8.73.0

Compare Source

This was a version bump only for typescript-eslint to align it with other projects, there were no code changes.

See GitHub Releases for more information.

You can read about our versioning strategy and releases on our website.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@changeset-bot

changeset-bot Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 135a97a

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@codecov

codecov Bot commented Nov 17, 2026 •

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (d365012) to head (135a97a).

Additional details and impacted files
@@            Coverage Diff            @@
##            master      #797   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            1         1           
  Lines            2         2           
=========================================
  Hits             2         2           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from a709406 to 135a97a Compare November 18, 2026 03:36
@renovate renovate Bot changed the title chore(deps): update all non-major dependencies to v8.73.0 chore(deps): update all non-major dependencies Nov 18, 2026
@renovate
renovate Bot merged commit 61eebc2 into master Nov 18, 2026
4 checks passed
@renovate
renovate Bot deleted the renovate/all-minor-patch branch November 18, 2026 06:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants