Skip to content

chore(deps): update all non-major dependencies#46

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch
Open

chore(deps): update all non-major dependencies#46
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/all-minor-patch

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Mar 23, 2026

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence Type Update Pending
@nuxt/devtools (source) 3.2.33.2.4 age confidence devDependencies patch
@nuxt/test-utils 4.0.04.0.3 age confidence devDependencies patch
actions/checkout v6.0.2v6.0.3 age confidence action patch
actions/setup-node v6.3.0v6.4.0 age confidence action minor
defu ^6.1.4^6.1.7 age confidence dependencies patch
pnpm (source) 10.32.110.34.1 age confidence packageManager minor
vitest (source) 4.1.04.1.8 age confidence devDependencies patch
vue-tsc (source) 3.2.53.3.3 age confidence devDependencies minor 3.3.4

Release Notes

nuxt/devtools (@​nuxt/devtools)

v3.2.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
nuxt/test-utils (@​nuxt/test-utils)

v4.0.3

Compare Source

4.0.3 is the next patch release.

👉 Changelog

compare changes

🩹 Fixes
  • runtime-utils: Lazily import root-component in mount + render helpers (#​1665)
  • runtime-utils: Insert compilerOptions conditionally (#​1659)
  • config: Enable sourcemaps when vitest coverage is enabled (#​1674)
  • module: Exclude test files from Nuxt plugin registration (#​1666)
  • runtime-utils: Provide NuxtLink isActive slot props (#​1640)
  • e2e: Wait for HTTP readiness before resolving startServer (#​1675)
🏡 Chore
❤️ Contributors

v4.0.2

Compare Source

👉 Changelog

compare changes

🩹 Fixes
  • config: Respect override dev value (#​1602)
🤖 CI
  • Use pnpm publish to resolve workspace dependencies (#​1651)
❤️ Contributors

v4.0.1

Compare Source

👉 Changelog

compare changes

🩹 Fixes
  • config: Rename deps.optimizer.web to client for vitest4 (#​1593)
  • runtime-utils: Fix mockNuxtImport types when using string target (#​1592)
  • config: Pass non-project options for non-nuxt simple setup (#​1582)
  • config: Do not import defineConfig from vite (1aa5e8748)
  • runtime: Handle ResourceLoader removal in jsdom v28 (#​1611)
  • config,vitest-environment: Directly import peerDeps (#​1617)
  • runtime-utils: Align mount options merge w/ vue-test-utils (#​1610)
  • vitest-environment: Avoid vitest/environments import warning (#​1627)
  • runtime: Avoid error when vue/test-utils is not installed (#​1646)
  • config: Prefer project h3 version if present (#​1641)
🏡 Chore
  • Bump vitest-environment-nuxt versions (f5ec72127)
  • Use workspace dependency (14fb254a7)
  • Example playwright config improve type annotation for devices (#​1581)
  • pkg-pr-new prerelease vitest-environment-nuxt (#​1601)
  • Allow explicit any (633c93c2a)
  • Switch unit test target to dir and move type unit tests to test:types (#​1618)
  • Update lockfile (8306abf00)
✅ Tests
  • Add failing test for stubbed global provide (#​1314)
  • Update assertions deprecated in vitest 4.1 (#​1629)
  • Change example/workspace to use glob based projects setup (#​1585)
🤖 CI
  • Pin github actions to full-length commit shas (2832fd6d5)
  • Avoid checkout for reproduction comment (e4e67ab09)
  • Rename workflow (99318b9fc)
  • Correctly publish pkg-pr-new prerelease (#​1598)
❤️ Contributors
actions/checkout (actions/checkout)

v6.0.3

Compare Source

actions/setup-node (actions/setup-node)

v6.4.0

Compare Source

unjs/defu (defu)

v6.1.7

Compare Source

compare changes

🩹 Fixes
  • defu.d.cts: Export Defu types (#​157)
📦 Build
  • Correct the types export entry (#​160)
❤️ Contributors

v6.1.6

Compare Source

compare changes

📦 Build
❤️ Contributors

v6.1.5

Compare Source

compare changes

🩹 Fixes
  • Prevent prototype pollution via __proto__ in defaults (#​156)
  • Ignore inherited enumerable properties (11ba022)
🏡 Chore
✅ Tests
  • Add more tests for plain objects (b65f603)
🤖 CI
❤️ Contributors
pnpm/pnpm (pnpm)

v10.34.1: pnpm 10.34.1

Compare Source

Patch Changes

  • Reject pnpm-lock.yaml entries whose remote tarball resolution: block is missing the integrity field. Previously the worker that extracts a downloaded tarball skipped hash verification when no integrity was supplied and minted a fresh one from the unverified bytes, so an attacker who could both alter the lockfile (e.g. via a pull request that strips integrity:) and serve modified content at the referenced tarball URL could install a tampered package without any error — including under --frozen-lockfile. pnpm now fails closed at lockfile-read time with ERR_PNPM_MISSING_TARBALL_INTEGRITY. Git-hosted tarballs (gitHosted: true or a URL on codeload.github.com / bitbucket.org / gitlab.com) and file: tarballs are exempt — the commit SHA in a git-host URL and the user-controlled local path already anchor the bytes.

Platinum Sponsors

Bit

Gold Sponsors

Sanity Discord Vite
SerpApi CodeRabbit Stackblitz
Workleap Nx

v10.34.0: pnpm 10.34

Compare Source

Minor Changes

  • Treat tarball-integrity mismatches against the lockfile as a hard failure by default. Previously, pnpm install (non-frozen) would log ERR_PNPM_TARBALL_INTEGRITY, silently re-resolve from the registry, and overwrite the locked integrity — which meant a compromised registry, proxy, or republished version could substitute attacker-controlled content on a clean machine even though the project shipped a committed lockfile.

    pnpm install now exits with ERR_PNPM_TARBALL_INTEGRITY and a hint pointing at the new opt-in flag.

    The only opt-in is pnpm install --update-checksums — narrowly scoped to refreshing the locked integrity values from what the registry currently serves. Mirrors yarn's flag of the same name. A warning still prints when the bypass takes effect so the operation is auditable.

    --force and pnpm update deliberately do not bypass the integrity check. They are routine refresh operations; silently overwriting a locked integrity in those flows would erase the protection a committed lockfile is supposed to provide. --frozen-lockfile behavior is unchanged. --fix-lockfile keeps its documented purpose (filling in missing lockfile entries) and is also not a bypass.

Patch Changes

  • Pin unscoped per-registry settings (_authToken, _auth, username/_password, tokenHelper, inline cert/key) to the registry declared in the same config source at load time, so a later layer overriding registry= (workspace .npmrc, pnpm-workspace.yaml, CLI --registry) cannot redirect a credential or client certificate authored for a different host. A deprecation warning is emitted whenever an unscoped per-registry setting is encountered, naming the source and the URL it was pinned to. Reported by JUNYI LIU.
  • Fixed minimumReleaseAge handling when cached metadata is abbreviated. The npm registry returns abbreviated package metadata (without the per-version time field) by default, which made the maturity check throw ERR_PNPM_MISSING_TIME whenever cached abbreviated metadata was reused. pnpm now upgrades cached abbreviated metadata to the full document via a follow-up fetch when minimumReleaseAge is active, persists the upgrade to the on-disk cache so subsequent installs skip the extra fetch, and lets ERR_PNPM_MISSING_TIME from the cache fast-path fall through to the network fetch even under strict mode.
  • Reject git resolutions whose commit field is not a 40-character hexadecimal SHA before invoking git. A malicious lockfile could otherwise smuggle a value such as --upload-pack=<command> through git fetch / git checkout, which on SSH or local-file transports executes the supplied command.
  • Reject patch files whose diff --git headers reference paths outside the patched package directory. Previously a malicious .patch file added via a pull request could write, delete, or rename arbitrary files reachable by the user running pnpm install.
  • Fixed --prefix=<dir> not being honored when locating the workspace root. The --prefix → dir rename was applied after workspace detection, so workspace settings declared in <dir>/pnpm-workspace.yaml were not loaded when pnpm was invoked from outside <dir> #​11535.
  • Reject dependency aliases that contain path-traversal segments (such as @x/../../../../../.git/hooks) when reading them from a package manifest or symlinking them into node_modules. A malicious registry package could otherwise use a transitive dependency key to make pnpm install create symlinks at attacker-chosen paths outside the intended node_modules directory.

Platinum Sponsors

Bit

Gold Sponsors

Sanity Discord Vite
SerpApi CodeRabbit Stackblitz
Workleap Nx

v10.33.4: pnpm 10.33.4

Compare Source

Patch Changes

  • Pin the integrity of git-hosted tarballs (codeload.github.com, gitlab.com, bitbucket.org) in the lockfile so that subsequent installs detect a tampered or substituted tarball and refuse to install it. Previously the lockfile only stored the tarball URL for git dependencies, so a compromised git host or a man-in-the-middle could serve arbitrary code on later installs without lockfile changes.

    A new gitHosted: true field is recorded on git-hosted tarball resolutions in the lockfile, letting every reader/writer route them by a single typed check instead of pattern-matching the tarball URL in each call site. Lockfiles written by older pnpm versions are enriched on load (URL fallback) so the field can be relied on uniformly across the codebase.

  • Fix a regression where pnpm --recursive --filter '!<pkg>' run/exec/test/add would include the workspace root in the matched projects. The workspace root is now correctly excluded by default when only negative --filter arguments are provided, matching the documented behavior. To include the root, pass --include-workspace-root #​11341.

Platinum Sponsors

Bit

Gold Sponsors

Sanity Discord Vite
SerpApi CodeRabbit Stackblitz
Workleap Nx

v10.33.3

Compare Source

v10.33.2

Compare Source

v10.33.1: pnpm 10.33.1

Compare Source

Patch Changes
  • When a project's packageManager field selects pnpm v11 or newer, commands that v10 would have passed through to npm (version, login, logout, publish, unpublish, deprecate, dist-tag, docs, ping, search, star, stars, unstar, whoami, etc.) are now handed over to the wanted pnpm, which implements them natively. Previously they silently shelled out to npm — making, for example, pnpm version --help print npm's help on a project with packageManager: pnpm@11.0.0-rc.3 #​11328.
Platinum Sponsors
Bit
Gold Sponsors
Sanity Discord Vite
SerpApi CodeRabbit Stackblitz
Workleap Nx

v10.33.0

Compare Source

vitest-dev/vitest (vitest)

v4.1.8

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.7

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v4.1.6

Compare Source

   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v4.1.5

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.4

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.3

Compare Source

   🚀 Experimental Features
   🐞 Bug Fixes
    View changes on GitHub

v4.1.2

Compare Source

This release bumps Vitest's flatted version and removes version pinning to resolve flatted's CVE related issues (#​9975).

   🐞 Bug Fixes
    View changes on GitHub

v4.1.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
  • Mark TestProject.testFilesList internal properly  -  by @​sapphi-red

Note

PR body was truncated to here.


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • "on Monday"
  • 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 requested a review from IO-Fire as a code owner March 23, 2026 00:42
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch from 9dd51aa to 69c98f3 Compare March 23, 2026 18:05
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from 96f06c9 to 5e4d72c Compare April 7, 2026 13:30
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 2 times, most recently from edafdd0 to 558c35b Compare April 9, 2026 10:07
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 4 times, most recently from cf0d1f9 to 9eac9ee Compare April 22, 2026 14:11
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from a5b7aaf to a613d6d Compare May 4, 2026 09:35
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from c981e80 to 7dd7688 Compare May 11, 2026 18:36
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 3 times, most recently from e90d08a to eeb049c Compare May 18, 2026 12:33
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 57d4bfa to 23f0524 Compare May 26, 2026 15:45
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 5 times, most recently from 1bb5d83 to 3c120ec Compare June 2, 2026 12:07
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch from 3c120ec to 6282b57 Compare June 3, 2026 19:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants