Skip to content

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

Merged
sapphi-red merged 1 commit into
mainfrom
renovate/all-minor-patch
Nov 2, 2026
Merged

fix(deps): update all non-major dependencies#23966
sapphi-red merged 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Nov 2, 2026 •
edited
Loading

Copy link
Copy Markdown
Contributor

Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@babel/parser (source) ^7.29.11 β†’ ^7.29.12 age confidence devDependencies patch
@builder.io/qwik (source) ^1.20.2 β†’ ^1.20.3 age confidence dependencies patch
@rolldown/plugin-babel (source) 0.2.4 β†’ 0.3.0 age confidence minor
autoprefixer ^10.6.1 β†’ ^10.6.2 age confidence dependencies patch
baseline-browser-mapping ^2.11.32 β†’ ^2.11.34 age confidence devDependencies patch
browserslist ^4.29.4 β†’ ^4.29.5 age confidence dependencies patch
eslint (source) 10.13.0 β†’ 10.14.0 age confidence minor
eslint-plugin-regexp ^3.3.1 β†’ ^3.3.2 age confidence devDependencies patch 3.3.3
magic-string ^1.4.3 β†’ ^1.4.5 age confidence dependencies patch
magic-string ^1.4.3 β†’ ^1.4.5 age confidence devDependencies patch
oxfmt (source) ^0.74.0 β†’ ^0.75.0 age confidence devDependencies minor
oxlint (source) ^1.89.0 β†’ ^1.90.0 age confidence devDependencies minor
pnpm (source) 12.15.0 β†’ 12.16.1 age confidence packageManager minor
postcss (source) ^8.5.31 β†’ ^8.5.32 age confidence dependencies patch
preact (source) ^11.0.2 β†’ ^11.1.1 age confidence dependencies minor
sass ^1.106.1 β†’ ^1.107.1 age confidence devDependencies minor
sass-embedded ^1.106.1 β†’ ^1.107.1 age confidence devDependencies minor
semgrep/semgrep 1.182.1 β†’ 1.183.0 age confidence container minor
solid-js (source) ^1.9.17 β†’ ^1.9.18 age confidence dependencies patch
svelte (source) ^5.57.2 β†’ ^5.57.3 age confidence devDependencies patch
typescript-eslint (source) 8.72.0 β†’ 8.72.1 age confidence patch
vite-plugin-solid ^2.11.14 β†’ ^2.11.15 age confidence devDependencies patch
vitepress (source) ^2.0.0-alpha.20 β†’ ^2.0.0-alpha.21 age confidence devDependencies patch
vue-tsc (source) ^3.3.13 β†’ ^3.3.14 age confidence devDependencies patch
ws ^8.22.0 β†’ ^8.22.1 age confidence devDependencies patch

Release Notes

babel/babel (@​babel/parser)

v7.29.12

Compare Source

v7.29.12 (2026-10-29)

πŸ› Bug Fix
Committers: 2
QwikDev/qwik (@​builder.io/qwik)

v1.20.3

Compare Source

rolldown/plugins (@​rolldown/plugin-babel)

v0.3.0

Features
Bug Fixes
Miscellaneous Chores
Tests
postcss/autoprefixer (autoprefixer)

v10.6.2

Compare Source

  • Added /* autoprefixer: ignore next warning */ (by @​dualfroz).
  • Fixed losing unprefixed selectors in old browsers in grouping (by @​ybai08).
  • Fixed selector duplicates on multiple Autoprefixer runs.
  • Fixed case-insensitive pseudo-selector prefixing (by @​jakezwang).
  • Fixed -webkit-cross-fade() for images with numbers (by @​mkantautas).
  • Fixed source maps for Grid prefixes (by @​dualfroz).
web-platform-dx/baseline-browser-mapping (baseline-browser-mapping)

v2.11.34

Compare Source

v2.11.33

Compare Source

browserslist/browserslist (browserslist)

v4.29.5

Compare Source

eslint/eslint (eslint)

v10.14.0

Compare Source

Features

  • d23a7f9 feat: fix property descriptor handling in func-name-matching (#​21400) (xbinaryx)

Bug Fixes

Documentation

Chores

ota-meshi/eslint-plugin-regexp (eslint-plugin-regexp)

v3.3.2

Compare Source

Patch Changes
  • Add names to flat configurations for ESLint's config inspector. (#​1073)
Rich-Harris/magic-string (magic-string)

v1.4.5

Compare Source

Bug Fixes
Performance Improvements
  • cut allocations and quadratic lookups on the sourcemap and bundle paths (#​379) (d081246)
  • find the slice start chunk without scanning the list (#​378) (6ab6b04)

v1.4.4

Compare Source

Bug Fixes
oxc-project/oxc (oxfmt)

v0.75.0: oxfmt v0.75.0

Compare Source

πŸ› Bug Fixes
  • 5042019 formatter: Keep fill layout for array with comment after [ (#​28170) (leaysgur)
  • 9d37ff6 formatter: Use position-based comment checks for concise arrays (#​28169) (leaysgur)
  • 016c4a2 formatter: Keep a comment before } inside a JSX spread child (#​28103) (vidigoat)
  • 190bb1e formatter: Keep parens around an instantiation expression ending an operand through any tight parent (#​28168) (leaysgur)
  • a5314a1 formatter: Keep ; before in and instanceof class members (#​28166) (leaysgur)
  • 3a56e7c formatter: Keep closing HTML comments at the start of a line (#​28064) (Cameron)
  • 23d23d6 formatter_markdown: Honor range ignore inside directives (#​28164) (leaysgur)
  • 5f1fd3d formatter: Measure width heuristics by display width (#​28098) (leaysgur)
  • a5a52cf formatter: Keep parens around private in expressions (#​28096) (leaysgur)
  • 999496e formatter: Measure a short key by its display width (#​28026) (vidigoat)
  • 7e9aa44 formatter: Keep parens around a looser operand of an instantiation expression (#​28025) (vidigoat)
  • 6912d1f formatter: Keep an arrow signature that exactly fills the line for any body (#​27989) (leaysgur)
  • eb1d9f9 formatter_core: Count a flat line space in fits only when text follows (#​27987) (leaysgur)
⚑ Performance
πŸ“š Documentation
oxc-project/oxc (oxlint)

v1.90.0

Compare Source

πŸš€ Features
  • 831cdf1 oxlint: Require mininum oxlint-tsgolint version v7.0.2005 (#​28118) (camc314)
  • d1b00f4 linter/typescript: Implement no-unsafe-enum-assignment rule (#​28117) (camc314)
  • 165c91f linter/typescript/await-thenable: Support allowMixedPromiseArrays option (#​28116) (camc314)
pnpm/pnpm (pnpm)

v12.16.1: pnpm 12.16.1

Compare Source

This release fixes pnpm install hanging on a cold store in workspaces that install Cargo crates, and pnpm pack shipping a file that files excludes by name.

Patch Changes

  • pnpm install no longer hangs on a cold store in a workspace that also installs Cargo crates or a Rust toolchain.

  • pnpm pack and pnpm publish now apply a files entry that names a file after the glob and directory entries, as npm does. A file excluded by name, such as !dist/index.js, stays out even when a later dist/** matches it. A file named by its path, such as lib/secret.js, ships even when a later !lib/*.js matches it.

  • pnpm install no longer leaves a broken symlink in an injected workspace dependency when the package links to a file outside its published files and pnpm imports by hardlink. Installing a git dependency now skips internal directory symlinks when importing its files into the store.

  • pnpm install now relinks a command that a workspace project renames into the projects that depend on it when sharedWorkspaceLockfile is false pnpm/tasks#224.

  • pnpm install and pnpm rebuild now refresh privately hoisted .bin shims in node_modules/.pnpm/node_modules/.bin after a dependency build replaces a script target with a native executable #​17402.

  • pnpm install now reads a package's manifest to decide its peer dependencies when it updates an existing lockfile, as it does when it resolves from scratch.

  • Commands, pnpm --version, pnpm self-update, and invocations with unknown flags now apply the same packageManager and devEngines.packageManager settings when switching to the pinned pnpm version or recording it in pnpm-lock.yaml. --config.<key> flags and lockfileDir now reach the version switch and lockfile sync on every entry point. Unreadable settings in pnpm-workspace.yaml or the global config.yaml that do not affect the pin decision no longer block the version switch pnpm/tasks#222.

  • pnpm now accepts the --cache-dir <dir> flag, as in pnpm install --cache-dir /tmp/pnpm-cache #​17422.

  • When the version or range given to pnpm unpublish matches every published version, the error now says so and shows the same command with --force. Before, the error suggested running pnpm unpublish <pkg>@<version>, the command that had just failed.

Platinum Sponsors

Bit OpenAI Notion
CodeRabbit

Gold Sponsors

Sanity Discord Vite
SerpApi Stackblitz Workleap
Nx Latitude

v12.16.0: pnpm 12.16

Compare Source

This release adds a global --env-file flag, updates to a symlinked pnpm-lock.yaml, and pnpm setup --no-modify-path. It also fixes two security issues, in zstd decompression and in signing.

Minor Changes

  • Added a repeatable global --env-file <path> flag to load environment variables from dotenv-style files before running a command. Later files override earlier files, variables already in the environment are preserved, and loaded variables are visible to user-level .npmrc interpolation and lifecycle scripts #​7111.

  • pnpm can now update a pnpm-lock.yaml that is a symlink. List the directories the lockfile may link into in the symlinkedLockfileTargetDirs setting, in the global config or with PNPM_CONFIG_SYMLINKED_LOCKFILE_TARGET_DIRS. pnpm writes the update to the file the symlink points to if that file is inside one of these directories. The symlink stays in place. pnpm ignores this setting in pnpm-workspace.yaml #​17222.

  • Added a --no-modify-path option to pnpm setup. It installs pnpm without adding it to PATH, leaving the shell config file, the Windows registry, and the GitHub Actions environment files unchanged. pnpm setup then prints the lines to add yourself get.pnpm.io#37.

Patch Changes
Security

  • Fixed memory exposure and allocation handling vulnerabilities when processing zstd-compressed data #​17388.

  • Signing in pnpm and pnpr no longer uses arithmetic that may leak the private key through timing. This covers shared artifacts, OCI registry tokens, and OIDC login state advisory.

Installing packages

  • A dependency symlink that pnpm cannot point at the wanted target now fails the install with an error that names the link. This happens when the filesystem still serves the old link after pnpm removed it, as a node_modules served by a virtual filesystem does. pnpm used to remove the link again without end and crashed with a segmentation fault once the thread ran out of stack.

  • Concurrent workspace installs no longer lose store-index rows when initializing the shared SQLite index #​17388.

  • Agent skill links now keep the same target across installs when a package version is installed with several sets of peer dependencies. An install no longer fails with ERR_PNPM_AGENT_SKILL_PATH_OCCUPIED on a skill link that pnpm created for another of those copies #​17319.

  • pnpm now fails at once, without retrying, when a downloaded package archive contains a rejected entry path #​17205.

  • pnpm now builds a git-hosted dependency in every new location it links the dependency into, such as a new global virtual store slot or a fresh node_modules. When the side-effects cache holds the build output, pnpm restores it from there. Before, only the install that fetched the dependency built it. This also fixes dependencies that are already in the store #​17224.

  • Changes a preResolution hook makes to the lockfiles now take effect. The hook now also runs when pnpm installs from an up-to-date lockfile. An error thrown by the hook now fails the install.

  • A custom fetcher in the pnpmfile can now call fetchers.directory to fetch a package from a local directory. The call rejects with ERR_PNPM_TARBALL_INTEGRITY if the lockfile pins an archive integrity for the package. Previously, calling fetchers.directory failed with a TypeError.

  • packageImportMethod: copy now also applies to packages that have lifecycle scripts or patches. On a filesystem that supports block cloning, such as ReFS or a Dev Drive on Windows, these packages were cloned #​17195.

  • With nodeLinker: hoisted and autoInstallPeers: false, a package that workspace projects use with different peer versions is now installed once per peer variant, so each project's copy resolves that project's peer #​17395.

  • Under nodeLinker: hoisted, pnpm install now leaves a patched package that is already in place alone. The same holds for a package whose peers include a patched package, such as every package peering on a patched react-native #​17188.

  • With nodeLinker: hoisted, an install that stops partway no longer leaves the next install trusting the packages it was replacing. Before, reverting the change that started the stopped install, such as a patch edit, kept the half-replaced package in node_modules.

Repeat installs and changed settings

  • A repeat pnpm install now acts on a change to these settings. Before, it reported "Already up to date".

    • storeDir or virtualStoreDir: it recreates node_modules.
    • globalVirtualStoreDir: it links the packages from the new directory.
    • virtualStoreDirMaxLength: it renames the virtual store directories.
    • dangerouslyAllowAllBuilds turned on: it runs the builds it skipped.
    • trustLockfile turned off: it verifies the lockfile.

  • pnpm add, pnpm remove, and pnpm update now fail if node_modules does not match the current settings. Run pnpm install to recreate it. Previously, these commands removed and reinstalled node_modules without asking. They report:

    • ERR_PNPM_UNEXPECTED_STORE if node_modules was linked from a different store.
    • ERR_PNPM_UNEXPECTED_VIRTUAL_STORE if it was linked from a different virtual store directory.
    • ERR_PNPM_MODULES_BREAKING_CHANGE if it was installed by an incompatible pnpm version, or if node_modules/.modules.yaml cannot be read.
    • ERR_PNPM_NODE_LINKER_DIFF if it was installed with a different nodeLinker.

    pnpm update now also fails with ERR_PNPM_HOIST_PATTERN_DIFF and the other errors pnpm add reports for a changed hoist pattern or virtualStoreDirMaxLength.

  • An install filtered to some workspace projects now fails if node_modules was installed with a different nodeLinker, hoistPattern, publicHoistPattern, store, or virtual store. Before, it recreated node_modules and left the projects it skipped without their dependencies. A pnpm install of the whole workspace still recreates node_modules pnpm/tasks#217.

  • pnpm install and the verifyDepsBeforeRun check now notice an edited patch file when sharedWorkspaceLockfile is false.

  • pnpm install now takes its fast path in a workspace with patchedDependencies when the previous install ran with another major version of pnpm.

  • pnpm install now relinks the bins of a workspace package when its bin field changes, including with --frozen-lockfile and an unchanged lockfile. A filtered install relinks them in the selected projects, and the next install that covers the remaining projects relinks them there #​17324.

  • pnpm install now removes command shims from node_modules/.bin when a workspace dependency renames or removes an entry from its bin field pnpm/tasks#211.

Resolving dependencies and the lockfile

  • A package that a plain range and a <prefix>: specifier both resolve from one registry is now recorded once in pnpm-lock.yaml and installed once. The lockfile key names the registry a package resolved from. When that registry declares a prefix, through prefix in registries or through namedRegistries, the package is keyed <name>@<prefix>:<version> however its dependency was written: with the prefix, as a plain range its scope routes to that registry, or through the default registry. Before, the plain range was keyed <name>@<version>, so one tarball was installed twice and instanceof checks and module singletons broke between the two copies. The same name and version served by two registries still get separate entries. When several prefixes declare one registry, its packages are keyed by the lexicographically smallest prefix.

    If a scope you route reaches a registry that also declares a prefix, your next pnpm install re-keys those entries, which shows up as a lockfile diff. Commit it. pnpm install --frozen-lockfile installs the lockfile as recorded.

  • pnpm install now resolves a scope's packages again when the scope is routed to another registry in registries. Before, the lockfile kept the versions and integrity resolved from the old registry, so the install failed when the new registry did not serve a locked version or served different content. pnpm records in the workspace state which registry each scope routed to, so a fresh clone without that record installs the lockfile as recorded. Changing the default registry resolves nothing again, and pnpm install --frozen-lockfile is unchanged.

  • When autoDedupe is off, a workspace project's dependencies now resolve from its own ranges, like they do with sharedWorkspaceLockfile: false. Previously, another project's narrower range could hold them back. For example, ajv: "*" now resolves to the latest Ajv even if another project depends on ajv@^6. Packages that a project lists in peerDependencies still follow the versions other projects use. pnpm dedupe and installs with autoDedupe: true still pick one version that satisfies every range. Set autoDedupe: true if CI runs pnpm dedupe --check #​17235.

  • An optional dependency written with a named-registry prefix, such as work:^1.0.0, now fails the install when it cannot be resolved but the lockfile already has a matching entry from that registry. Such a dependency was skipped, which removed its entries from the lockfile.

  • With injectWorkspacePackages: true, a workspace: dependency written as a relative path, such as workspace:../lib-a, in a workspace package now resolves from that package's directory #​17284.

  • Fixed pnpm install failing with ERR_PNPM_UNSUPPORTED_PROTOCOL when a workspace package injected through a relative path, such as workspace:../lib, has catalog: dependencies. Their catalog entries now resolve the way they do for a package injected by name #​17280.

  • pnpm dedupe now refreshes cached registry metadata while re-resolving locked versions #​17208.

  • pnpm dedupe --check no longer fails when the only difference is a deprecated notice that the registry added or removed after the lockfile was written #​17198.

  • Installs delegated to a pnpr server now resolve every prefix declared for a registry URL. A dependency or lockfile entry that used the second of two prefixes for the same registry, such as zeta: next to work: in namedRegistries, failed on the server pnpm/tasks#204.

  • Registry revisions are now addressed at <registry>/<name>@<version>+r<revision> pnpm/tasks#208.

Adding packages and global packages

  • pnpm add <pkg>@<tag> and pnpm add <pkg>@<range> now install the version the tag or range resolves to, even when the saved range allows a newer one #​17234.

  • pnpm add <pkg> without a version now installs the version under the dist-tag set by the tag setting. An npm: alias or a jsr: dependency without a version resolves that tag too. The setting is read from pnpm-workspace.yaml, the global config, PNPM_CONFIG_TAG, and --config.tag, and defaults to latest.

  • pnpm add now accepts the lowercase short options -p, -d, -o, and -e as aliases of --save-prod, --save-dev, --save-optional, and --save-exact.

  • pnpm -D install <pkg> now saves the package to devDependencies. An add option such as -D or -E written before install <pkg> was rejected as an unexpected argument.

  • pnpm add -T now reports that the short option is ambiguous and points to --save-types and --tilde.

  • Global packages installed with pnpm add -g are now linked from the global virtual store, so global packages that share dependencies share one copy. Set virtualStoreType: project to give each global install its own virtual store.

  • pnpm add -g and the other --global commands now fail with ERR_PNPM_CONFIG_CONFLICT_VIRTUAL_STORE_DIR_WITH_GLOBAL when --virtual-store-dir is passed. A custom --hoist-pattern fails with ERR_PNPM_CONFIG_CONFLICT_HOIST_PATTERN_WITH_GLOBAL. Passing --link-workspace-packages, --shared-workspace-lockfile, or --config.lockfile-dir with --global also fails, with the matching ERR_PNPM_CONFIG_CONFLICT_*_WITH_GLOBAL code.

Registries, proxies, and login

  • pnpm now reads the strictSsl and localAddress settings from pnpm-workspace.yaml, the global config.yaml, PNPM_CONFIG_* environment variables, and --config.* options. This includes pnpm self-update and the download of the pnpm version pinned in packageManager. Before, pnpm read them only from .npmrc as strict-ssl and local-address and ignored the other sources pnpm/tasks#201.

  • When Corepack runs pnpm and the native binary has to be downloaded, the d

[!IMPORTANT]
βœ‚ PR body was truncated to here.

Configuration

πŸ“… Schedule: (UTC)

  • Branch creation
    • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
  • 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.

@renovate renovate Bot added the dependencies Pull requests that update a dependency file label Nov 2, 2026
@renovate
renovate Bot force-pushed the renovate/all-minor-patch branch from 60d3c72 to 4c18d71 Compare November 2, 2026 06:29
@sapphi-red
sapphi-red merged commit b3cb057 into main Nov 2, 2026
21 of 22 checks passed
@sapphi-red
sapphi-red deleted the renovate/all-minor-patch branch November 2, 2026 06:34
This was referenced Nov 5, 2026
Merged
Merged
Merged
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@sapphi-red sapphi-red sapphi-red approved these changes

Assignees

No one assigned

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@sapphi-red