Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Sep 30, 2025

This PR contains the following updates:

Package Change Age Confidence Type Update
@typescript-eslint/eslint-plugin (source) ^8.41.0 -> ^8.46.0 age confidence devDependencies minor
chalk ^5.6.0 -> ^5.6.2 age confidence devDependencies patch
esbuild ^0.25.9 -> ^0.25.10 age confidence devDependencies patch
eslint (source) ^9.34.0 -> ^9.37.0 age confidence devDependencies minor
jest (source) ^30.1.1 -> ^30.2.0 age confidence devDependencies minor
jiti ^2.5.1 -> ^2.6.1 age confidence dependencies minor
node (source) 22.19.0 -> 22.20.0 age confidence minor
pnpm (source) 10.15.0 -> 10.18.2 age confidence minor
release-it ^19.0.4 -> ^19.0.5 age confidence devDependencies patch
typescript (source) ^5.9.2 -> ^5.9.3 age confidence devDependencies patch
typescript-eslint (source) ^8.41.0 -> ^8.46.0 age confidence devDependencies minor

Release Notes

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

v8.46.0

Compare Source

🚀 Features
  • eslint-plugin: [no-unsafe-member-access] add allowOptionalChaining option (#​11659)
  • rule-schema-to-typescript-types: clean up and make public (#​11633)
🩹 Fixes
  • eslint-plugin: [prefer-readonly-parameter-types] ignore tagged primitives (#​11660)
  • typescript-estree: forbid abstract method and accessor to have implementation (#​11657)
  • eslint-plugin: removed error type previously deprecated (#​11674)
  • eslint-plugin: [no-deprecated] ignore deprecated export imports (#​11603)
  • eslint-plugin: [unbound-method] improve wording around this: void and binding (#​11634)
  • rule-tester: deprecate TestCaseError#type and LintMessage#nodeType (#​11628)
  • eslint-plugin: [no-floating-promises] remove excess parentheses in suggestions (#​11487)
❤️ Thank You

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

v8.45.0

Compare Source

🚀 Features
  • eslint-plugin: expose rule name via RuleModule interface (#​11616)
🩹 Fixes
  • eslint-plugin: [prefer-nullish-coalescing] ignoreBooleanCoercion should not apply to top-level ternary expressions (#​11614)
  • eslint-plugin: [no-base-to-string] check if superclass is ignored (#​11617)
❤️ Thank You

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

v8.44.1

Compare Source

🩹 Fixes
  • eslint-plugin: [await-thenable] should not report passing values to promise aggregators which may be a promise in an array literal (#​11611)
  • eslint-plugin: [no-unsafe-enum-comparison] support unions of literals (#​11599)
  • eslint-plugin: [no-base-to-string] make ignoredTypeNames match type names without generics (#​11597)
❤️ Thank You

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

v8.44.0

Compare Source

🚀 Features
  • eslint-plugin: [await-thenable] report invalid (non-promise) values passed to promise aggregator methods (#​11267)
🩹 Fixes
  • eslint-plugin: [no-unnecessary-type-conversion] ignore enum members (#​11490)
❤️ Thank You

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

v8.43.0

Compare Source

🚀 Features
  • typescript-estree: disallow empty type parameter/argument lists (#​11563)
🩹 Fixes
  • eslint-plugin: [prefer-return-this-type] don't report an error when returning a union type that includes a classType (#​11432)
  • eslint-plugin: [no-deprecated] should report deprecated exports and reexports (#​11359)
  • eslint-plugin: [no-floating-promises] allowForKnownSafeCalls now supports function names (#​11423, #​11430)
  • eslint-plugin: [consistent-type-exports] fix declaration shadowing (#​11457)
  • eslint-plugin: [no-unnecessary-type-conversion] only report ~~ on integer literal types (#​11517)
  • scope-manager: exclude Program from DefinitionBase node types (#​11469)
  • eslint-plugin: [no-non-null-assertion] do not suggest optional chain on LHS of assignment (#​11489)
  • type-utils: add union type support to TypeOrValueSpecifier (#​11526)
❤️ Thank You

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

v8.42.0

Compare Source

🩹 Fixes
  • deps: update eslint monorepo to v9.33.0 (#​11482)

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

chalk/chalk (chalk)

v5.6.2

Compare Source

  • Fix vulnerability in 5.6.1, see: #​656
evanw/esbuild (esbuild)

v0.25.10

Compare Source

  • Fix a panic in a minification edge case (#​4287)

    This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value undefined in this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):

    function identity(x) { return x }
    identity({ y: identity(123) })
  • Fix @supports nested inside pseudo-element (#​4265)

    When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as ::placeholder for correctness. The CSS nesting specification says the following:

    The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.

    However, it seems like this behavior is different for nested at-rules such as @supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:

    /* Original code */
    ::placeholder {
      color: red;
      body & { color: green }
      @​supports (color: blue) { color: blue }
    }
    
    /* Old output (with --supported:nesting=false) */
    ::placeholder {
      color: red;
    }
    body :is() {
      color: green;
    }
    @​supports (color: blue) {
       {
        color: blue;
      }
    }
    
    /* New output (with --supported:nesting=false) */
    ::placeholder {
      color: red;
    }
    body :is() {
      color: green;
    }
    @​supports (color: blue) {
      ::placeholder {
        color: blue;
      }
    }
eslint/eslint (eslint)

v9.37.0

Compare Source

v9.36.0

Compare Source

v9.35.0

Compare Source

jestjs/jest (jest)

v30.2.0

Compare Source

Chore & Maintenance
  • [*] Update example repo for testing React Native projects (#​15832)
  • [*] Update jest-watch-typeahead to v3 (#​15830)

v30.1.3

Compare Source

Fixes
  • Fix unstable_mockModule with node: prefixed core modules.

v30.1.2

Compare Source

unjs/jiti (jiti)

v2.6.1

Compare Source

compare changes

🩹 Fixes
  • interop: Only passthrough default if it is not a promise (#​408)
📦 Build
  • Revert to terser-webpack-plugin (#​407)
🏡 Chore
❤️ Contributors

v2.6.0

Compare Source

compare changes

🔥 Performance
  • Lazy load babel transform (#​405)
🩹 Fixes
  • cjs-interop: Handle function default exports (#​396)
  • Always use native for node: specifiers (#​392)
📦 Build
🏡 Chore
✅ Tests
  • Update deno and bun native test ignores (df844f8)
  • New bench script (6404427)
❤️ Contributors
  • Pooya Parsa (@​pi0)
  • Volodymyr Kolesnykov (@​sjinks)
  • Jungwoo LEE <jungwoo3490@​naver.com>
nodejs/node (node)

v22.20.0

Compare Source

pnpm/pnpm (pnpm)

v10.18.2

Compare Source

Patch Changes
  • pnpm outdated --long should work #​10040.
  • Replace ndjson with split2. Reduce the bundle size of pnpm CLI #​10054.
  • pnpm dlx should request the full metadata of packages, when minimumReleaseAge is set #​9963.
  • pnpm version switching should work when the pnpm home directory is in a symlinked directory #​9715.
  • Fix EPIPE errors when piping output to other commands #​10027.

v10.18.1

Compare Source

Patch Changes
  • Don't print a warning, when --lockfile-only is used #​8320.
  • pnpm setup creates a command shim to the pnpm executable. This is needed to be able to run pnpm self-update on Windows #​5700.
  • When using pnpm catalogs and running a normal pnpm install, pnpm produced false positive warnings for "skip adding to the default catalog because it already exists". This warning now only prints when using pnpm add --save-catalog as originally intended.

v10.18.0

Compare Source

Minor Changes
  • Added network performance monitoring to pnpm by implementing warnings for slow network requests, including both metadata fetches and tarball downloads.

    Added configuration options for warning thresholds: fetchWarnTimeoutMs and fetchMinSpeedKiBps.
    Warning messages are displayed when requests exceed time thresholds or fall below speed minimums

    Related PR: #​10025.

Patch Changes
  • Retry filesystem operations on EAGAIN errors #​9959.
  • Outdated command respects minimumReleaseAge configuration #​10030.
  • Correctly apply the cleanupUnusedCatalogs configuration when removing dependent packages.
  • Don't fail with a meaningless error when scriptShell is set to false #​8748.
  • pnpm dlx should not fail when minimumReleaseAge is set #​10037.

v10.17.1

Compare Source

Patch Changes
  • When a version specifier cannot be resolved because the versions don't satisfy the minimumReleaseAge setting, print this information out in the error message #​9974.
  • Fix state.json creation path when executing pnpm patch in a workspace project #​9733.
  • When minimumReleaseAge is set and the latest tag is not mature enough, prefer a non-deprecated version as the new latest #​9987.

v10.17.0

Compare Source

Minor Changes
  • The minimumReleaseAgeExclude setting now supports patterns. For instance:

    minimumReleaseAge: 1440
    minimumReleaseAgeExclude:
      - "@&#8203;eslint/*"

    Related PR: #​9984.

Patch Changes
  • Don't ignore the minimumReleaseAge check, when the package is requested by exact version and the packument is loaded from cache #​9978.
  • When minimumReleaseAge is set and the active version under a dist-tag is not mature enough, do not downgrade to a prerelease version in case the original version wasn't a prerelease one #​9979.

v10.16.1

Compare Source

Patch Changes
  • The full metadata cache should be stored not at the same location as the abbreviated metadata. This fixes a bug where pnpm was loading the abbreviated metadata from cache and couldn't find the "time" field as a result #​9963.
  • Forcibly disable ANSI color codes when generating patch diff #​9914.

v10.16.0

Compare Source

Minor Changes
  • There have been several incidents recently where popular packages were successfully attacked. To reduce the risk of installing a compromised version, we are introducing a new setting that delays the installation of newly released dependencies. In most cases, such attacks are discovered quickly and the malicious versions are removed from the registry within an hour.

    The new setting is called minimumReleaseAge. It specifies the number of minutes that must pass after a version is published before pnpm will install it. For example, setting minimumReleaseAge: 1440 ensures that only packages released at least one day ago can be installed.

    If you set minimumReleaseAge but need to disable this restriction for certain dependencies, you can list them under the minimumReleaseAgeExclude setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:

    minimumReleaseAgeExclude:
      - webpack

    Related issue: #​9921.

  • Added support for finders #​9946.

    In the past, pnpm list and pnpm why could only search for dependencies by name (and optionally version). For example:

    pnpm why minimist
    

    prints the chain of dependencies to any installed instance of minimist:

    verdaccio 5.20.1
    ├─┬ handlebars 4.7.7
    │ └── minimist 1.2.8
    └─┬ mv 2.1.1
      └─┬ mkdirp 0.5.6
        └── minimist 1.2.8
    

    What if we want to search by other properties of a dependency, not just its name? For instance, find all packages that have react@17 in their peer dependencies?

    This is now possible with "finder functions". Finder functions can be declared in .pnpmfile.cjs and invoked with the --find-by=<function name> flag when running pnpm list or pnpm why.

    Let's say we want to find any dependencies that have React 17 in peer dependencies. We can add this finder to our .pnpmfile.cjs:

    module.exports = {
      finders: {
        react17: (ctx) => {
          return ctx.readManifest().peerDependencies?.react === "^17.0.0";
        },
      },
    };

    Now we can use this finder function by running:

    pnpm why --find-by=react17
    

    pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    └── graphql-tag 2.12.6
    

    It is also possible to print out some additional information in the output by returning a string from the finder. For example, with the following finder:

    module.exports = {
      finders: {
        react17: (ctx) => {
          const manifest = ctx.readManifest();
          if (manifest.peerDependencies?.react === "^17.0.0") {
            return `license: ${manifest.license}`;
          }
          return false;
        },
      },
    };

    Every matched package will also print out the license from its package.json:

    @&#8203;apollo/client 4.0.4
    ├── @&#8203;graphql-typed-document-node/core 3.2.0
    │   license: MIT
    └── graphql-tag 2.12.6
        license: MIT
    
Patch Changes
  • Fix deprecation warning printed when executing pnpm with Node.js 24 #​9529.
  • Throw an error if nodeVersion is not set to an exact semver version #​9934.
  • pnpm publish should be able to publish a .tar.gz file #​9927.
  • Canceling a running process with Ctrl-C should make pnpm run return a non-zero exit code #​9626.

v10.15.1

Compare Source

Patch Changes
  • Fix .pnp.cjs crash when importing subpath #​9904.
  • When resolving peer dependencies, pnpm looks whether the peer dependency is present in the root workspace project's dependencies. This change makes it so that the peer dependency is correctly resolved even from aliased npm-hosted dependencies or other types of dependencies #​9913.
release-it/release-it (release-it)

v19.0.5

Compare Source

microsoft/TypeScript (typescript)

v5.9.3

Compare Source

typescript-eslint/typescript-eslint (typescript-eslint)

v8.46.0

Compare Source

🚀 Features
❤️ Thank You

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

v8.45.0

Compare Source

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

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

v8.44.1

Compare Source

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

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

v8.44.0

Compare Source

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

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

v8.43.0

Compare Source

🩹 Fixes
  • eslint-plugin: [no-deprecated] should report deprecated exports and reexports (#​11359)
❤️ Thank You

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

v8.42.0

Compare Source

🚀 Features
🩹 Fixes
  • typescript-eslint: handle non-normalized windows paths produced by jiti (#​11546)
❤️ Thank You

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


Configuration

📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, on day 1 of the month ( * 0-3 1 * * ) in timezone Pacific/Auckland, 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.

@renovate renovate bot added the dependencies Pull requests that update a dependency file label Sep 30, 2025
@coderabbitai
Copy link

coderabbitai bot commented Sep 30, 2025

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Comment @coderabbitai help to get the list of available commands and usage tips.

@renovate renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from afed8e9 to 870bebd Compare October 6, 2025 18:13
@renovate renovate bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from e7985bd to 6e90cb7 Compare October 10, 2025 01:34
@Codex- Codex- force-pushed the renovate/all-minor-patch branch from 6e90cb7 to b4e48c3 Compare October 10, 2025 01:39
@renovate
Copy link
Contributor Author

renovate bot commented Oct 10, 2025

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@codecov-commenter
Copy link

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (4f266b6) to head (200973f).

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #180   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            3         3           
  Lines           31        33    +2     
  Branches         4         4           
=========================================
+ Hits            31        33    +2     

☔ View full report in Codecov by Sentry.
📢 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.

@Codex- Codex- merged commit f53ac85 into main Oct 10, 2025
6 checks passed
@Codex- Codex- deleted the renovate/all-minor-patch branch October 10, 2025 01:46
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.

3 participants