chore(deps): update all non-major dependencies - #1845
Merged
Merged
Conversation
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
14 times, most recently
from
August 16, 2026 13:26
5ed8d59 to
65ccc9a
Compare
renovate
Bot
force-pushed
the
renovate/all-non-major
branch
from
August 16, 2026 18:14
65ccc9a to
b40bbdf
Compare
Timeless0911
approved these changes
Aug 17, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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:
~2.1.12→~2.1.13~2.1.12→~2.1.13^2.0.1→^2.1.01.14.7→1.14.82.2.1→2.2.3^0.11.6→^0.11.8^0.11.6→^0.11.8^0.11.6→^0.11.8^0.11.6→^0.11.8^4.4.2→^4.4.3^10.5.7→^10.5.8^10.5.7→^10.5.8^10.5.7→^10.5.8^10.5.7→^10.5.8^10.5.7→^10.5.8^10.5.7→^10.5.8^10.5.7→^10.5.8^10.5.7→^10.5.8^7.0.0→^7.0.1v4.0.2→v4.0.35.0.0-beta.5→5.0.0-beta.6^1.1.0→^1.2.0^4.68.0→^4.68.111.20.0→11.22.0>=11.20.0→>=11.22.0v6.0.9→v6.0.10^10.5.7→^10.5.8^10.5.7→^10.5.8^3.4.1→^3.4.2^3.4.1→^3.4.2^3.4.1→^3.4.2^3.4.1→^3.4.2^3.4.1→^3.4.2^3.4.1→^3.4.2^5.56.8→^5.56.9^4.7.5→^4.7.6^0.7.59→^0.7.61^4.23.11→^4.23.12^3.3.9→^3.3.10^3.3.9→^3.3.10Release Notes
web-infra-dev/rsbuild (@rsbuild/core)
v2.1.13Compare Source
What's Changed
Full Changelog: web-infra-dev/rsbuild@v2.1.12...v2.1.13
rstackjs/rsbuild-plugin-toml (@rsbuild/plugin-toml)
v2.1.0Compare Source
What's Changed
df4cb1cby @renovate[bot] in #62d23441aby @renovate[bot] in #702499707by @renovate[bot] in #71New Contributors
Full Changelog: rstackjs/rsbuild-plugin-toml@v2.0.1...v2.1.0
rstackjs/rstack-doc-ui (@rstack-dev/doc-ui)
v1.14.8Compare Source
What's Changed
d23441aby @renovate[bot] in #1162499707by @renovate[bot] in #117Full Changelog: rstackjs/rstack-doc-ui@v1.14.7...v1.14.8
rstackjs/create-toolkit (@rstackjs/create-toolkit)
v2.2.3Compare Source
What's Changed
Full Changelog: rstackjs/create-toolkit@v2.2.2...v2.2.3
v2.2.2Compare Source
What's Changed
Full Changelog: rstackjs/create-toolkit@v2.2.1...v2.2.2
web-infra-dev/rstest (@rstest/adapter-rslib)
v0.11.8Compare Source
What's Changed
Bug Fixes 🐞
Full Changelog: web-infra-dev/rstest@v0.11.7...v0.11.8
v0.11.7Compare Source
What's Changed
New Features 🎉
Performance 🚀
Bug Fixes 🐞
Refactor 🔨
Document 📖
Other Changes
Full Changelog: web-infra-dev/rstest@v0.11.6...v0.11.7
shikijs/shiki (@shikijs/transformers)
v4.4.3Compare Source
🚀 Features
🐞 Bug Fixes
View changes on GitHub
storybookjs/storybook (@storybook/addon-docs)
v10.5.8Compare Source
storybookjs/storybook (@storybook/addon-onboarding)
v10.5.8Compare Source
10.5.8
storybookjs/storybook (@storybook/react)
v10.5.8Compare Source
storybookjs/storybook (@storybook/vue3)
v10.5.8Compare Source
testing-library/jest-dom (@testing-library/jest-dom)
v7.0.1Compare Source
dorny/paths-filter (dorny/paths-filter)
v4.0.3Compare Source
privatenumber/get-tsconfig (get-tsconfig)
v5.0.0-beta.6Compare Source
Bug Fixes
Rich-Harris/magic-string (magic-string)
v1.2.0Compare Source
Features
1.1.1 (2026-08-12)
Bug Fixes
v1.1.1Compare Source
Features
1.1.1 (2026-08-12)
Bug Fixes
streamich/memfs (memfs)
v4.68.1Compare Source
What's Changed
.unlink()should not delete empty directories by @streamich in #1278Full Changelog: streamich/memfs@v4.68.0...v4.68.1
pnpm/pnpm (pnpm)
v11.22.0Compare Source
v11.21.0: pnpm 11.21Compare Source
Minor Changes
Added interactive group selection to
pnpm update --global --interactive.Running
pnpm setup,pnpm self-update, or a command that modifies the global installation (such aspnpm add --global) throughsudonow prints a warning. pnpm keeps global packages and configuration in the invoking user's home directory, so running these commands as root silently operates on the root user's home directory instead of yours. They will fail withERR_PNPM_SUDO_NOT_SUPPORTEDin pnpm v12. Read-only global commands (such aspnpm bin --global) are unaffected.Patch Changes
Fixed pnpm failing to start under asynchronous Node.js module loaders when no
.pnpmfile.mjsexists pnpm/pnpm#11701.Fixed
minimumReleaseAgefallback for custom dist-tags so the selected version does not exceed the registry’s original tag target.Removing a dependency from
package.jsonand reinstalling no longer re-resolves the dependency graph. The importer's entry is dropped frompnpm-lock.yaml, anything it made unreachable is pruned, and a catalog entry that loses its last referent is removed — all without registry access. Installs still fall back to a full resolution when a package that stays resolves a peer dependency through the removed one, since that would change the surviving package's entry rather than only prune.Changing a catalog entry to a different exact version no longer re-resolves the dependency graph. The package is replaced in
pnpm-lock.yamldirectly, reusing the same check thepnpm.overridesfast path applies: every locked dependency of the package must still satisfy the new version's manifest. Installs fall back to a full resolution when anything other than the catalog reaches the package — an importer that depends on it directly, or another package that depends on it — since the graph would then need both versions.Fixed a CI regression where
github:owner/repodependencies (and other shorthand Git specifiers) would fail to install withPermission denied (publickey)on CI runners that lack SSH keys. The Git resolver no longer records an SSH URL unless the user explicitly wrote one (e.g.git+ssh://orgit@host:...):429 Too Many Requests, so host throttling of CI runners is no longer mistaken for a private repository.git ls-remoteaccess is now tried before SSH, so a public repository whose visibility probe fails still resolves to a portable HTTPS URL instead of an SSH URL that only works where SSH keys are configured.codeload.github.com, which would fail to download for a private repository); it stays a regulargitresolution so installs can use ambient Git credentials such as credential helpers and tokens.Note that a private repository that is reachable both over authenticated HTTPS and over SSH now resolves to its HTTPS URL, where previous versions recorded the SSH URL.
Fixes pnpm/pnpm#13276.
ng buildandnuxt buildnow work under the global virtual store: pnpm's built-in compatibility extensions add thetslibdependency that@angular/builduses without declaring and theunplugindependency that@nuxt/vite-builderv4 uses without declaring.Fixed
link:dependencies underenableGlobalVirtualStoreso linked children are materialized and slots remain isolated by their resolved link targets.An install that skips resolution because
pnpm-lock.yamlis already up to date now reacts fully to packages the lockfile removed — for example after pulling a lockfile in which a dependency was deleted. The hoist layer is recomputed, so a package that became hoistable when a direct dependency was removed is hoisted, andpendingBuildsentries for removed packages are dropped instead of staying pending forever.The held-back-update warning printed by
pnpm updateno longer fires whenminimumReleaseAgeis the actual reason a newer version was not picked. The warning's baseline now applies the same maturity cutoff as the pick itself, so it no longer wrongly attributes the hold-back to "your manifests and already installed dependencies" or recommends an override that would defeat the age gate. See #13071.Checking whether
ignoredOptionalDependenciesis up to date no longer reorders the configured patterns. The check sorted them in place, which could move an!exclusion ahead of the pattern it excludes from and flip which optional dependencies were ignored.Changing
autoInstallPeers,dedupePeers,peersSuffixMaxLength,excludeLinksFromLockfile, orinjectWorkspacePackagesno longer re-resolves the dependency graph when the lockfile proves the setting cannot affect it: no package or project declares a peer dependency for the peer settings, and no project depends on a directory or on another workspace project for the link and injection settings. The new setting is recorded inpnpm-lock.yamland the install proceeds from the existing resolution. Every other case still falls back to a full resolution.Adding, editing, or removing an entry in
patchedDependenciesno longer re-resolves the dependency graph. Resolution never reads a patch — it only records the patch file's hash against the package it matches — so the install now rewrites the affected entries inpnpm-lock.yamland materializes the patched package from the store instead. Installs still fall back to a full resolution when the patched package is reachable as a peer dependency, and when the new configuration would leave a patch unused whileallowUnusedPatchesis off, soERR_PNPM_UNUSED_PATCHis still reported.Resolving a private git repository no longer blocks on an interactive credential prompt:
git ls-remotenow fails fast with an authentication error when git has no credentials for the repository #13522.Lockfile verification now honors offline mode by using cached registry metadata instead of reaching the registry. When the required metadata is not available locally, verification reports the same
ERR_PNPM_NO_OFFLINE_METAcondition used by offline resolution.POSIX shell shims now follow symbolic links before computing
basedir, preventing execution failures when a shim is invoked via an external symlink onPATH#13405.The automatic
packageManagerversion switch works again on registries whose tarball URLs point at a different host than the registry itself (load-balanced feed proxies, Artifactory-style mirrors). Package-manager entries are now always recorded with integrity-only resolutions — the download URL is derived from the trusted bootstrap registry instead — and entries persisted in an invalid shape by an earlier pnpm are discarded and re-resolved instead of failing every command #13619.Registries that serve no npm signature metadata (private mirrors and feed proxies commonly strip
dist.signatures) no longer break the automaticpackageManagerversion switch andpnpm self-update#13147. When the configured registry cannot provide a verifiable signature, pnpm now fetches the signature fromregistry.npmjs.organd verifies it against the same embedded npm keys over the installed integrity — which proves exactly the same thing. If no signature can be obtained from either source (for example, both are unreachable, or the registry publishes only ashasum), pnpm proceeds with a warning instead of failing, but only when the packages resolve through a registry configured in the user's own (non-project) configuration; the download stays pinned by the lockfile integrity, and a signature that exists but does not validate still fails the switch.pnpm fetch, and any install run withvirtualStoreOnly, no longer writes a.pnp.cjsloader undernodeLinker: pnp. These installs populate the virtual store without linking the project, so the loader would have claimed the project resolves out of a store it was never linked into. The importer links andnode_modules/.package-map.jsonwere already skipped; the PnP loader now follows the same rule.Prevent pnpm from removing project files when
modulesDirresolves to the project root.Speed up installs after adding
ignoredOptionalDependenciespatterns by removing newly ignored optional dependencies and pruning packages that are no longer reachable without resolving the dependency graph again.When a failed install re-copies a bin script from the store, rerunning
pnpm installnow reapplies the executable bit to the bin instead of leaving it non-executable #12742.pnpm root -gandpnpm bin -gnow print warnings to stderr instead of stdout, so their stdout stays a clean, machine-readable path. Previously, running either command with--globalin a project that pins a package manager (e.g. via thepackageManagerfield) printed a warning like[WARN] Using --global skips the package manager check for this projectahead of the path, breaking programs that capture the output as a path #13672.In pnpm 12,
pnpm root -gandpnpm prefix -gare now supported (they previously failed withERR_PNPM_CLI_ROOT_GLOBAL_UNSUPPORTED/ERR_PNPM_CLI_PREFIX_GLOBAL_UNSUPPORTED), and the reporter output ofdlx,create,config,sbom,with,store,prefix,root, andbingoes to stderr, matching pnpm 11.pnpm setupno longer makes Node.js print aMODULE_TYPELESS_PACKAGE_JSONwarning aboutdist/worker.json every command. Thepackage.jsonit writes next to a standalone executable now declares"type": "module".pnpm updatewithout saving no longer records a version that the manifest's range excludes. The kept range stays authoritative: a requested version outside it is skipped with a warning, and a requested range, a dist tag, or--latestresolves within it instead of past it. Previously each of these could write a lockfile entry that contradicted its own specifier, which the nextpnpm install --frozen-lockfilerejected withERR_PNPM_OUTDATED_LOCKFILE#12764.pnpm version -r --jsonnow outputs[]instead of human-readable text when no pending changes existpnpm/pnpm#13217.Platinum Sponsors
This PR was generated by Mend Renovate. View the repository job log.