chore(deps): update all non-major dependencies #152
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.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
9.32.0
->9.36.0
0.1.1
->0.1.12
22.17.0
->22.18.6
v5.4.3
->v5.5.1
9.32.0
->9.36.0
16.3.0
->16.4.0
10.13.1+sha512.37ebf1a5c7a30d5fabe0c5df44ee8da4c965ca0c5af3dbab28c3a1681b70a256218d05c81c9c0dcf767ef6b8551eb5b960042b9ed4300c59242336377e01cfad
->10.17.0
5.8.3
->5.9.2
8.38.0
->8.44.0
Release Notes
eslint/eslint (@eslint/js)
v9.36.0
Compare Source
v9.35.0
Compare Source
v9.34.0
Compare Source
v9.33.0
Compare Source
codecov/codecov-action (codecov/codecov-action)
v5.5.1
Compare Source
What's Changed
codecov-cli
version reference example by @webknjaz in #1774Full Changelog: https://github.com/codecov/codecov-action/compare/v5.5.0..v5.5.1
v5.5.0
Compare Source
What's Changed
Full Changelog: https://github.com/codecov/codecov-action/compare/v5.4.3..v5.5.0
eslint/eslint (eslint)
v9.36.0
Compare Source
v9.35.0
Compare Source
v9.34.0
Compare Source
v9.33.0
Compare Source
sindresorhus/globals (globals)
v16.4.0
Compare Source
8b8a2d6
pnpm/pnpm (pnpm)
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.v10.15.1
Compare Source
Patch Changes
.pnp.cjs
crash when importing subpath #9904.v10.15.0
Compare Source
Minor Changes
cleanupUnusedCatalogs
configuration. When set totrue
, pnpm will remove unused catalog entries during installation #9793.@*/pnpm-plugin-*
#9780.pnpm config get
now prints an INI string for an object value #9797.pnpm config get
now accepts property paths (e.g.pnpm config get catalog.react
,pnpm config get .catalog.react
,pnpm config get 'packageExtensions["@​babel/parser"].peerDependencies["@​babel/types"]'
), andpnpm config set
now accepts dot-leading or subscripted keys (e.g.pnpm config set .ignoreScripts true
).pnpm config get --json
now prints a JSON serialization of config value, andpnpm config set --json
now parses the input value as JSON.Patch Changes
pnpm create
command, must verify whether the node version is supported even if a cache already exists #9775.*/*
to theAccept
header to avoid getting a 406 error on AWS CodeArtifact #9862.pnpm dlx pkg --help
doesn't pass--help
topkg
#9823.v10.14.0
Compare Source
Minor Changes
Added support for JavaScript runtime resolution
Declare Node.js, Deno, or Bun in
devEngines.runtime
(insidepackage.json
) and let pnpm download and pin it automatically.Usage example:
How it works:
pnpm install
resolves your specified range to the latest matching runtime version.Why this is better:
useNodeVersion
andexecutionEnv.nodeVersion
)executionEnv.nodeVersion
). So, different projects in a workspace can use different runtimes.devEngines.runtime
setting will install the runtime locally, which we will improve in future versions of pnpm by using a shared location on the computer.Related PR: #9755.
Add
--cpu
,--libc
, and--os
topnpm install
,pnpm add
, andpnpm dlx
to customizesupportedArchitectures
via the CLI #7510.Patch Changes
pnpm add
downloads packages whoselibc
differ frompnpm.supportedArchitectures.libc
.dlx
to parse CLI flags and options between thedlx
command and the command to run or between thedlx
command and--
#9719.pnpm install --prod
should removing hoisted dev dependencies #9782.pnpm install
to incorrectly assume the lockfile is up to date after changing a local tarball that has peers dependencies.microsoft/TypeScript (typescript)
v5.9.2
Compare Source
typescript-eslint/typescript-eslint (typescript-eslint)
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
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.42.0
Compare Source
🚀 Features
🩹 Fixes
❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.41.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.40.0
Compare Source
🩹 Fixes
plugin
,parser
, andconfigs
that are compatible with bothdefineConfig()
andtseslint.config()
(#11475)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.39.1
Compare Source
🩹 Fixes
file://
urls in stack trace when inferringtsconfigRootDir
(#11464)❤️ Thank You
You can read about our versioning strategy and releases on our website.
v8.39.0
Compare Source
🚀 Features
❤️ Thank You
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.
This PR was generated by Mend Renovate. View the repository job log.