fix(deps): update all non-major dependencies #23
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.
This PR contains the following updates:
^5.2.0
->^5.3.0
^2.2.0
->^2.2.1
^0.5.1
->^0.5.4
^22.13.9
->^22.14.1
^10.0.3
->^10.1.0
^9.21.0
->^9.24.0
^1.29.1
->^1.29.3
10.5.2
->10.8.0
v4.0.0
->v4.1.0
^4.34.9
->^4.40.0
^0.6.3
->^0.6.10
^5.8.2
->^5.8.3
^2.2.0
->^2.3.2
^6.2.0
->^6.2.6
^3.0.7
->^3.1.1
Release Notes
sxzz/eslint-config (@sxzz/eslint-config)
v5.3.0
Compare Source
🚀 Features
View changes on GitHub
sxzz/test-utils (@sxzz/test-utils)
v0.5.4
Compare Source
🏎 Performance
View changes on GitHub
v0.5.3
Compare Source
🚀 Features
View changes on GitHub
v0.5.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
antfu-collective/bumpp (bumpp)
v10.1.0
Compare Source
🚀 Features
View changes on GitHub
eslint/eslint (eslint)
v9.24.0
Compare Source
v9.23.0
Compare Source
v9.22.0
Compare Source
parcel-bundler/lightningcss (lightningcss)
v1.29.3
Compare Source
::details-content
and::target-text
selectors – @philipp-spiess in https://github.com/parcel-bundler/lightningcss/pull/930:placeholder-shown
selector name across browsers – @Marukome0743 in https://github.com/parcel-bundler/lightningcss/pull/929/* cssmodules-pure-no-check */
comments – @jantimon in https://github.com/parcel-bundler/lightningcss/pull/898c03a7e7
v1.29.2
Compare Source
Browsers::load_browserslist
by @CPunisher in https://github.com/parcel-bundler/lightningcss/pull/8952284653
pnpm/pnpm (pnpm)
v10.8.0
Compare Source
Minor Changes
Experimental. A new hook is supported for updating configuration settings. The hook can be provided via
.pnpmfile.cjs
. For example:Now you can use the
pnpm add
command with the--config
flag to install new configurational dependencies #9377.Patch Changes
!/
inpnpm-workspace.yaml
. This fixes a regression introduced by #9169.pnpm audit --fix
should update the overrides inpnpm-workspace.yaml
.pnpm link
should update overrides inpnpm-workspace.yaml
, not inpackage.json
#9365.v10.7.1
: pnpm 10.7.1Compare Source
Patch Changes
pnpm config set
should convert the settings to their correct type before adding them topnpm-workspace.yaml
#9355.pnpm config get
should read auth related settings via npm CLI #9345.~/
in a path in.npmrc
with the home directory #9217.Platinum Sponsors
Gold Sponsors
v10.7.0
Compare Source
Minor Changes
pnpm config get
andlist
also show settings set inpnpm-workspace.yaml
files #9316.It should be possible to use env variables in
pnpm-workspace.yaml
setting names and value.Add an ability to patch dependencies by version ranges. Exact versions override version ranges, which in turn override name-only patches. Version range
*
is the same as name-only, except that patch application failure will not be ignored.For example:
The above configuration would apply
patches/foo-3.patch
to[email protected]
,patches/foo-2.patch
to allfoo
versions which satisfy^2.0.0
except2.1.0
, andpatches/foo-1.patch
to the remainingfoo
versions.pnpm config set --location=project
saves the setting to apnpm-workspace.yaml
file if no.npmrc
file is present in the directory #9316.Rename
pnpm.allowNonAppliedPatches
topnpm.allowUnusedPatches
. The old name is still supported but it would print a deprecation warning message.Add
pnpm.ignorePatchFailures
to manage whether pnpm would ignore patch application failures.If
ignorePatchFailures
is not set, pnpm would throw an error when patches with exact versions or version ranges fail to apply, and it would ignore failures from name-only patches.If
ignorePatchFailures
is explicitly set tofalse
, pnpm would throw an error when any type of patch fails to apply.If
ignorePatchFailures
is explicitly set totrue
, pnpm would print a warning when any type of patch fails to apply.Patch Changes
v10.6.5
Compare Source
v10.6.4
: pnpm 10.6.4Compare Source
Patch Changes
pnpm dlx
with--allow-build
flag #9263.use-node-version
should not cause pnpm itself to break #9276.Platinum Sponsors
Gold Sponsors
v10.6.3
Compare Source
Patch Changes
pnpm install --prod=false
should not crash, when executed in a project with apnpm-workspace.yaml
file #9233. This fixes regression introduced via #9211.Add the missing
node-options
config torecursive run
#9180.Removed a branching code path that only executed when
dedupe-peer-dependents=false
. We believe this internal refactor will not result in behavior changes, but we expect it to make future pnpm versions behave more consistently for projects that overridededupe-peer-dependents
to false. There should be less unique bugs from turning offdedupe-peer-dependents
.See details in #9259.
v10.6.2
Compare Source
Patch Changes
pnpm self-update
should always update the version in thepackageManager
field ofpackage.json
.pnpm patch-commit
will now use the same filesystem as the store directory to compare and create patch files.--loglevel=error
is used.peerDependencyRules
should be set inpnpm-workspace.yaml
to take effect.v10.6.1
Compare Source
Patch Changes
--silent
reporting is used.--loglevel
is set toerror
, don't show installation summary, execution time, and big tarball download progress.package.json
#9226.approve-builds
command, if package.json containsonlyBuiltDependencies
orignoredBuiltDependencies
, the selected dependency package will continue to be written intopackage.json
.v10.6.0
Compare Source
Minor Changes
pnpm-workspace.yaml
can now hold all the settings that.npmrc
accepts. The settings should use camelCase #9211.pnpm-workspace.yaml
example:Projects using a
file:
dependency on a local tarball file (i.e..tgz
,.tar.gz
,.tar
) will see a performance improvement during installation. Previously, using afile:
dependency on a tarball caused the lockfile resolution step to always run. The lockfile will now be considered up-to-date if the tarball is unchanged.Patch Changes
pnpm self-update
should not leave a directory with a broken pnpm installation if the installation fails.fast-glob
replace withtinyglobby
to reduce the size of the pnpm CLI dependencies #9169.pnpm deploy
should not remove fields from the deployed package'spackage.json
file #9215.pnpm self-update
should not read the pnpm settings from thepackage.json
file in the current working directory.pnpm deploy
creating apackage.json
without theimports
andlicense
field #9193.pnpm update -i
should list only packages that have newer versions #9206.catalogs
section of thepnpm-lock.yaml
file to be removed whendedupe-peer-dependents=false
on a filtered install. #9112pnpm/action-setup (pnpm/action-setup)
v4.1.0
Compare Source
Add support for
package.yaml
#156.rollup/rollup (rollup)
v4.40.0
Compare Source
2025-04-12
Features
eval
warnings on first render and only when the call is not tree-shaken (#5892)Bug Fixes
Pull Requests
treeshake: false
breaking destructured namespace imports (@Skn0tt)v4.39.0
Compare Source
2025-04-02
Features
Bug Fixes
id
property as optional in the filter for theresolveId
hook (#5896)Pull Requests
v4.38.0
Compare Source
2025-03-29
Features
.filter
option inresolveId
,load
andtransform
hooks (#5882)Pull Requests
v4.37.0
Compare Source
2025-03-23
Features
export
keyword (#5871)Bug Fixes
Pull Requests
v4.36.0
Compare Source
2025-03-17
Features
renderDynamicImport
hook to provide information about static dependencies of the imported module (#5870)Bug Fixes
Pull Requests
v4.35.0
Compare Source
2025-03-08
Features
Pull Requests
sxzz/tsdown (tsdown)
v0.6.10
Compare Source
No significant changes
View changes on GitHub
v0.6.9
Compare Source
🐞 Bug Fixes
View changes on GitHub
v0.6.8
Compare Source
No significant changes
View changes on GitHub
v0.6.7
Compare Source
🚀 Features
View changes on GitHub
v0.6.6
Compare Source
🚀 Features
ResolveDtsPlugin
- by @sxzz (2a89c)🐞 Bug Fixes
View changes on GitHub
v0.6.5
Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
microsoft/TypeScript (typescript)
v5.8.3
Compare Source
unjs/unplugin (unplugin)
v2.3.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.3.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.3.0
Compare Source
🚀 Features
resolveId/load/transform.filter
, deprecateloadInclude
&transformInclude
- by @sxzz in https://github.com/unjs/unplugin/issues/494 (b9fde)View changes on GitHub
v2.2.2
Compare Source
🐞 Bug Fixes
View changes on GitHub
v2.2.1
Compare Source
🐞 Bug Fixes
View changes on GitHub
vitejs/vite (vite)
v6.2.6
Compare Source
Please refer to CHANGELOG.md for details.
v6.2.5
Compare Source
Please refer to CHANGELOG.md for details.
v6.2.4
Compare Source
Please refer to CHANGELOG.md for details.
[
v6.2.3
](https://redirect.github.com/viteConfiguration
📅 Schedule: Branch creation - "* 0-3 * * 1" (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.