chore(deps): update all non-major dependencies #593
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Note
Mend has cancelled the proposed renaming of the Renovate GitHub app being renamed to
mend[bot]
.This notice will be removed on 2025-10-07.
This PR contains the following updates:
22.18.1
->22.18.8
v0.1.0
->v0.1.1
16.1.6
->16.2.3
0.30.18
->0.30.19
10.15.1
->10.18.0
4.50.1
->4.52.4
5.9.2
->5.9.3
Release Notes
danielroe/provenance-action (danielroe/provenance-action)
v0.1.1
Compare Source
compare changes
🚀 Enhancements
📖 Documentation
@main
constraint for example (237ceea)❤️ Contributors
lint-staged/lint-staged (lint-staged)
v16.2.3
Compare Source
Patch Changes
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:
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 isreadonly string[]
and can't be mutated. Thanks @outslept!#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 arepackage.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 withchalk
anddebug
, 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 theprecommit
hook fail. This is similar to thegit 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, theDEBUG
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 chalk@5.6.1 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
orNO_COLOR=true
env variables.rich-harris/magic-string (magic-string)
v0.30.19
Compare Source
Bug Fixes
Features
replace(All)
support replacement for functions when the first parameter is a string (#304) (fd1d887)pnpm/pnpm (pnpm)
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
andfetchMinSpeedKiBps
.Warning messages are displayed when requests exceed time thresholds or fall below speed minimums
Related PR: #10025.
Patch Changes
minimumReleaseAge
configuration #10030.cleanupUnusedCatalogs
configuration when removing dependent packages.scriptShell
is set tofalse
#8748.pnpm dlx
should not fail whenminimumReleaseAge
is set #10037.v10.17.1
Compare Source
Patch Changes
minimumReleaseAge
setting, print this information out in the error message #9974.state.json
creation path when executingpnpm patch
in a workspace project #9733.minimumReleaseAge
is set and thelatest
tag is not mature enough, prefer a non-deprecated version as the newlatest
#9987.v10.17.0
Compare Source
Minor Changes
The
minimumReleaseAgeExclude
setting now supports patterns. For instance:Related PR: #9984.
Patch Changes
minimumReleaseAge
check, when the package is requested by exact version and the packument is loaded from cache #9978.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
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, settingminimumReleaseAge: 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 theminimumReleaseAgeExclude
setting. For instance, with the following configuration pnpm will always install the latest version of webpack, regardless of its release time:Related issue: #9921.
Added support for
finders
#9946.In the past,
pnpm list
andpnpm why
could only search for dependencies by name (and optionally version). For example:prints the chain of dependencies to any installed instance of
minimist
: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 runningpnpm list
orpnpm 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
:Now we can use this finder function by running:
pnpm will find all dependencies that have this React in peer dependencies and print their exact locations in the dependency graph.
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:
Every matched package will also print out the license from its
package.json
:Patch Changes
nodeVersion
is not set to an exact semver version #9934.pnpm publish
should be able to publish a.tar.gz
file #9927.pnpm run
return a non-zero exit code #9626.rollup/rollup (rollup)
v4.52.4
Compare Source
2025-10-03
Bug Fixes
Pull Requests
v4.52.3
Compare Source
2025-09-27
Bug Fixes
Pull Requests
fb197b7
(@renovate[bot])v4.52.2
Compare Source
2025-09-23
Bug Fixes
Pull Requests
v4.52.1
Compare Source
2025-09-23
Bug Fixes
Pull Requests
v4.52.0
Compare Source
2025-09-19
Features
output.onlyExplicitManualChunks
to turn off merging additional dependencies into manual chunks (#6087)Pull Requests
v4.51.0
Compare Source
2025-09-19
Features
Bug Fixes
Pull Requests
v4.50.2
Compare Source
2025-09-15
Bug Fixes
Pull Requests
microsoft/TypeScript (typescript)
v5.9.3
Compare Source
Configuration
📅 Schedule: Branch creation - "on Monday" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.