fix(deps): update all non-major dependencies by renovate[bot] · Pull Request #116 · basics/rxjs-collection

renovate · 2025-01-11T02:56:05Z

This PR contains the following updates:

Package	Change	Type	Update
@eslint/js (source)	`9.35.0` -> `9.37.0`	devDependencies	minor
@vitest/eslint-plugin	`1.3.12` -> `1.3.16`	devDependencies	patch
commitlint (source)	`20.0.0` -> `20.1.0`	devDependencies	minor
eslint (source)	`9.35.0` -> `9.37.0`	devDependencies	minor
eslint-plugin-perfectionist (source)	`4.15.0` -> `4.15.1`	devDependencies	patch
fast-equals	`5.2.2` -> `5.3.2`	dependencies	minor
lint-staged	`16.1.6` -> `16.2.3`	devDependencies	minor
node (source)	`22.19.0` -> `22.20.0`		minor
pnpm (source)	`10.15.0` -> `10.18.2`	uses-with	minor
semantic-release	`24.2.8` -> `24.2.9`	devDependencies	patch
tsx (source)	`4.20.5` -> `4.20.6`	devDependencies	patch
typescript (source)	`5.9.2` -> `5.9.3`	devDependencies	patch
typescript-eslint (source)	`8.44.0` -> `8.46.0`	devDependencies	minor

Release Notes

eslint/eslint (@eslint/js)

`v9.37.0`

Compare Source

`v9.36.0`

Compare Source

Features

47afcf6 feat: correct preserve-caught-error edge cases (#20109) (Francesco Trotta)

Bug Fixes

75b74d8 fix: add missing rule option types (#20127) (ntnyq)
1c0d850 fix: update eslint-all.js to use Object.freeze for rules object (#20116) (루밀LuMir)
7d61b7f fix: add missing scope types to Scope.type (#20110) (Pixel998)
7a670c3 fix: correct rule option typings in rules.d.ts (#20084) (Pixel998)

Documentation

b73ab12 docs: update examples to use defineConfig (#20131) (sethamus)
31d9392 docs: fix typos (#20118) (Pixel998)
c7f861b docs: Update README (GitHub Actions Bot)
6b0c08b docs: Update README (GitHub Actions Bot)
91f97c5 docs: Update README (GitHub Actions Bot)

Chores

12411e8 chore: upgrade @eslint/js@9.36.0 (#20139) (Milos Djermanovic)
488cba6 chore: package.json update for @eslint/js release (Jenkins)
bac82a2 ci: simplify renovate configuration (#19907) (唯然)
c00bb37 ci: bump actions/labeler from 5 to 6 (#20090) (dependabot[bot])
fee751d refactor: use defaultOptions in rules (#20121) (Pixel998)
1ace67d chore: update example to use defineConfig (#20111) (루밀LuMir)
4821963 test: add missing loc information to error objects in rule tests (#20112) (루밀LuMir)
b42c42e chore: disallow use of deprecated type property in core rule tests (#20094) (Milos Djermanovic)
7bb498d test: remove deprecated type property from core rule tests (#20093) (Pixel998)
e10cf2a ci: bump actions/setup-node from 4 to 5 (#20089) (dependabot[bot])
5cb0ce4 refactor: use meta.defaultOptions in preserve-caught-error (#20080) (Pixel998)
f9f7cb5 chore: package.json update for eslint-config-eslint release (Jenkins)
81764b2 chore: update eslint peer dependency in eslint-config-eslint (#20079) (Milos Djermanovic)

vitest-dev/eslint-plugin-vitest (@vitest/eslint-plugin)

conventional-changelog/commitlint (commitlint)

`v20.1.0`

Compare Source

Note: Version bump only for package commitlint

eslint/eslint (eslint)

`v9.37.0`

Compare Source

`v9.36.0`

Compare Source

azat-io/eslint-plugin-perfectionist (eslint-plugin-perfectionist)

`v4.15.1`

Compare Source

compare changes

🐞 Bug Fixes

sort-modules: Fix decorator dependencies not detected (86f1626)
sort-objects: Fix complex call expressions being ignored in calling function name pattern (20da679)
sort-variable-declarations: Fix destructured assignments dependencies not detected (1def9db)

❤️ Contributors

Hugo (@hugop95)

planttheidea/fast-equals (fast-equals)

`v5.3.2`

Compare Source

#154 - Use include with "files" instead of exclude with .npmignore (Thanks @43081j)
#155 - Upgrade build dependencies to resolve security vulnerabilities

`v5.3.1`

Compare Source

#153 - Avoid publishing .yarn folder

`v5.3.0`

Compare Source

#150 - Add support for unknownTagComparators in custom configuration (thanks to @mrcljx for the idea)

lint-staged/lint-staged (lint-staged)

`v16.2.3`

Compare Source

Patch Changes

#1669 27cd541 Thanks @iiroj! - When using --fail-on-changes, automatically hidden (partially) unstaged changes are no longer counted to make lint-staged fail.

`v16.2.2`

Compare Source

Patch Changes

#1667 699f95d Thanks @iiroj! - The backup stash will not be dropped when using --fail-on-changes and there are errors. When reverting to original state is disabled (via --no-revert or --fail-on-changes), hidden (partially) unstaged changes are still restored automatically so that it's easier to resolve the situation manually.

Additionally, the example for using the backup stash manually now uses the correct backup hash, if available:

% npx lint-staged --fail-on-changes
✔ Backed up original state in git stash (c18d55a3)
✔ Running tasks for staged files...
✖ Tasks modified files and --fail-on-changes was used!
↓ Cleaning up temporary files...

✖ lint-staged failed because `--fail-on-changes` was used.

Any lost modifications can be restored from a git stash:

  > git stash list --format="%h %s"
  c18d55a3 On main: lint-staged automatic backup
  > git apply --index c18d55a3

`v16.2.1`

Compare Source

Patch Changes

#1664 8277b3b Thanks @iiroj! - The built-in TypeScript types have been updated to more closely match the implementation. Notably, the list of staged files supplied to task functions is readonly string[] and can't be mutated. Thanks @outslept!
```
export default {
---  "*": (files: string[]) => void console.log('staged files', files)
+++  "*": (files: readonly string[]) => void console.log('staged files', files)
}
```
#1654 70b9af3 Thanks @iiroj! - This version has been published from GitHub Actions using Trusted Publishing for npm packages.
#1659 4996817 Thanks @iiroj! - Fix searching configuration files when the working directory is a subdirectory of a git repository, and there are package.json files in the working directory. This situation might happen when running lint-staged for a single package in a monorepo.
#1654 7021f0a Thanks @iiroj! - Return the caret semver range (^) to direct dependencies so that future patch and minor versions are allowed. This enables projects to better maintain and deduplicate their own transitive dependencies while not requiring direct updates to lint-staged. This was changed in 16.2.0 after the vulnerability issues with chalk and debug, which were also removed in the same version.

Given the recent vulnerabilities in the npm ecosystem, it's best to be very careful when updating dependencies.

`v16.2.0`

Compare Source

Minor Changes

#1615 99eb742 Thanks @iiroj! - Added a new option --fail-on-changes to make lint-staged exit with code 1 when tasks modify any files, making the precommit hook fail. This is similar to the git diff --exit-code option. Using this flag also implies the --no-revert flag which means any changes made my tasks will be left in the working tree after failing, so that they can be manually staged and the commit tried again.
#1611 cd05fd3 Thanks @rlorenzo! - Added a new option --continue-on-error so that lint-staged will run all tasks to completion even if some of them fail. By default, lint-staded will exit early on the first failure.
#1637 82fcc07 Thanks @iiroj! - Internal lint-staged errors are now thrown and visible in the console output. Previously they were caught with the process exit code set to 1, but not logged. This happens when, for example, there's a syntax error in the lint-staged configuration file.
#1647 a5ecc06 Thanks @iiroj! - Remove debug as a dependency due to recent malware issue; read more at debug-js/debug#1005. Because of this, the DEBUG environment variable is no longer supported — use the --debug to enable debugging
#1636 8db2717 Thanks @iiroj! - Added a new option --hide-unstaged so that lint-staged will hide all unstaged changes to tracked files before running tasks. The changes will be applied back after running the tasks. Note that the combination of flags --hide-unstaged --no-hide-partially-staged isn't meaningful and behaves the same as just --hide-unstaged.

Thanks to @ItsNickBarry for the idea and initial implementation in #1552.
#1648 7900b3b Thanks @iiroj! - Remove lilconfig to reduce reliance on third-party dependencies. It was used to find possible config files outside of those tracked in Git, including from the parent directories. This behavior has been moved directly into lint-staged and should work about the same.

Patch Changes

#1633 7f9e485 Thanks @dependabot! - Bumps listr2 from 9.0.3 to 9.0.4.
#1626 99d5a9b Thanks @iiroj! - Due to recent phishing attacks, for example [email protected] was released with malware. To avoid lint-staged's users being at risk the direct dependencies are pinned to exact versions, instead of allowing future patch versions with the caret (^) range.
#1588 035bbf2 Thanks @outslept! - Increase performance by listing staged files and searching for configuration concurrently.
#1645 deba3ad Thanks @iiroj! - Remove chalk as a dependency due to recent malware issue; read more at chalk/chalk#656.

If you are having trouble with ANSI color codes when using lint-staged, you can try setting either FORCE_COLOR=true or NO_COLOR=true env variables.

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.

semantic-release/semantic-release (semantic-release)

`v24.2.9`

Compare Source

Bug Fixes

deps: update dependency semver-diff to v5 (#3867) (a834948)

privatenumber/tsx (tsx)

`v4.20.6`

Compare Source

Bug Fixes

properly hide relaySignal from process.listeners() (#741) (710a424)

This release is also available on:

npm package (@latest dist-tag)

microsoft/TypeScript (typescript)

`v5.9.3`

Compare Source

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

`v8.46.0`

Compare Source

🚀 Features

typescript-eslint: export util types (#10848, #10849)

❤️ Thank You

Mister-Hope @Mister-Hope

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.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, 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.

bolt-new-by-stackblitz · 2025-01-11T02:56:08Z

Run & review this pull request in StackBlitz Codeflow.

github-actions · 2025-10-10T05:56:05Z

🎉 This PR is included in version @rxjs-collection/operators-v1.2.0-beta.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

github-actions · 2025-10-10T05:56:19Z

🎉 This PR is included in version @rxjs-collection/playground-v1.0.1-beta.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

renovate bot changed the title ~~chore(deps): update dependency eslint to v9.18.0~~ chore(deps): update all non-major dependencies Jan 12, 2025

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 8e4c84f to 56507c0 Compare January 19, 2025 00:25

renovate bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from 44d4243 to 2c3a63a Compare January 26, 2025 16:31

renovate bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from b655499 to 8b5111f Compare February 4, 2025 17:58

renovate bot force-pushed the renovate/all-minor-patch branch 9 times, most recently from bc864c0 to c39939d Compare February 13, 2025 16:44

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from b82a352 to 525fcd3 Compare February 22, 2025 05:54

renovate bot changed the title ~~chore(deps): update all non-major dependencies~~ fix(deps): update all non-major dependencies Feb 22, 2025

renovate bot force-pushed the renovate/all-minor-patch branch from 525fcd3 to 4961bb1 Compare February 23, 2025 22:43

renovate bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from f36449f to 9c9f620 Compare September 23, 2025 17:12

renovate bot changed the title ~~chore(deps): update all non-major dependencies~~ fix(deps): update all non-major dependencies Sep 23, 2025

renovate bot force-pushed the renovate/all-minor-patch branch 13 times, most recently from 1bc50de to 7415149 Compare October 1, 2025 02:57

renovate bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from 3956a61 to 5dd69fd Compare October 6, 2025 18:13

fix(deps): update all non-major dependencies

cc020c1

renovate bot force-pushed the renovate/all-minor-patch branch from 5dd69fd to cc020c1 Compare October 9, 2025 23:05

ThornWalli merged commit 80bd9be into beta Oct 10, 2025
1 check passed

ThornWalli deleted the renovate/all-minor-patch branch October 10, 2025 05:54

github-actions bot added the released on @beta label Oct 10, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Comments

fix(deps): update all non-major dependencies#116

fix(deps): update all non-major dependencies#116
ThornWalli merged 1 commit intobetafrom
renovate/all-minor-patch

renovate bot commented Jan 11, 2025 •

edited

Loading

Uh oh!

bolt-new-by-stackblitz bot commented Jan 11, 2025

Uh oh!

Uh oh!

github-actions bot commented Oct 10, 2025

Uh oh!

github-actions bot commented Oct 10, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

Comments

Conversation

renovate bot commented Jan 11, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Release Notes

Features

Bug Fixes

Documentation

Chores

🐞 Bug Fixes

❤️ Contributors

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Minor Changes

Patch Changes

Patch Changes

Bug Fixes

Bug Fixes

🚀 Features

❤️ Thank You

Configuration

Uh oh!

bolt-new-by-stackblitz bot commented Jan 11, 2025

Uh oh!

Uh oh!

github-actions bot commented Oct 10, 2025

Uh oh!

github-actions bot commented Oct 10, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

renovate bot commented Jan 11, 2025 •

edited

Loading