Skip to content

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

Merged
benjamincanac merged 2 commits into
mainfrom
renovate/all-minor-patch
Jun 15, 2026
Merged

chore(deps): update all non-major dependencies#2270
benjamincanac merged 2 commits into
mainfrom
renovate/all-minor-patch

Conversation

@renovate

@renovate renovate Bot commented Jun 8, 2026

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
@ai-sdk/anthropic (source) ^3.0.81^3.0.84 age confidence
@ai-sdk/mcp (source) ^1.0.45^1.0.50 age confidence
@ai-sdk/vue (source) ^3.0.193^3.0.204 age confidence
@comark/nuxt (source) ^0.3.1^0.4.0 age confidence
@iconify-json/lucide ^1.2.111^1.2.112 age confidence
@iconify-json/octicon ^1.2.26^1.2.28 age confidence
@iconify-json/simple-icons ^1.2.84^1.2.86 age confidence
@iconify-json/vscode-icons ^1.2.53^1.2.57 age confidence
@nuxt/eslint (source) ^1.15.2^1.16.0 age confidence
@nuxt/hints ^1.1.2^1.1.3 age confidence
@nuxt/scripts (source) ^1.1.1^1.2.1 age confidence
@nuxt/ui (source) ^4.8.1^4.8.2 age confidence
@takumi-rs/core (source) ^1.6.0^1.8.5 age confidence
@types/youtube (source) ^0.2.0^0.3.0 age confidence
@vercel/functions (source) ^3.6.1^3.7.1 age confidence
@vue/compiler-sfc (source) ^3.5.35^3.5.38 age confidence
@vue/test-utils ^2.4.10^2.4.11 age confidence
ai (source) ^6.0.193^6.0.204 age confidence
better-sqlite3 ^12.10.0^12.10.1 age confidence
eslint (source) ^10.4.1^10.5.0 age confidence
evlog (source) ^2.18.1^2.19.1 age confidence
happy-dom ^20.9.0^20.10.3 age confidence
motion-v ^2.2.1^2.3.0 age confidence
nuxt-og-image (source) ^6.5.1^6.6.0 age confidence
nuxt-schema-org (source) ^6.0.4^6.2.1 age confidence
pnpm (source) 11.5.011.6.0 age confidence
shaders ^2.5.128^2.5.130 age confidence
shiki (source) ^4.1.0^4.2.0 age confidence
vitest (source) ^4.1.7^4.1.8 age confidence
vue (source) ^3.5.35^3.5.38 age confidence
vue-tsc (source) ^3.3.3^3.3.5 age confidence

Release Notes

vercel/ai (@​ai-sdk/anthropic)

v3.0.84

Patch Changes

v3.0.82

Compare Source

Patch Changes
  • 2a91a17: feat(provider/anthropic): add support for claude-fable-5 and the fallbacks API parameter
vercel/ai (@​ai-sdk/mcp)

v1.0.49

Patch Changes
  • 3e8d9ba: fix(mcp): lock first sse endpoint received via event

  • 4fa7354: fix(mcp): prevent prototype-named tools from bypassing the schemas allowlist

    When using client.tools({ schemas }) to expose only an explicitly allowed
    subset of an MCP server's tools, the allowlist check used the in operator,
    which also matches inherited Object.prototype properties. A server-advertised
    tool named constructor, toString, __proto__, etc. would pass the check
    even though the developer never defined it in schemas, and was then exposed to
    the model and executable. The check now uses Object.hasOwn, so only
    explicitly defined tools are returned.

  • Updated dependencies [bfa5864]

  • Updated dependencies [f42aa79]

v1.0.47

Compare Source

Patch Changes
  • bf1d6bd: fix(mcp): prevent mcp oauth credential exfiltration during rediscovery

v1.0.46

Compare Source

Patch Changes
  • 1f817db: fix(mcp): await addClientAuthentication in token exchange and refresh
vercel/ai (@​ai-sdk/vue)

v3.0.203

Patch Changes

v3.0.201

Compare Source

Patch Changes
  • Updated dependencies [0c8c0ed]
    • ai@​6.0.201

v3.0.200

Compare Source

Patch Changes
  • Updated dependencies [14098e7]
  • Updated dependencies [2cabe9c]
    • ai@​6.0.200

v3.0.199

Compare Source

Patch Changes
  • Updated dependencies [49d9364]
    • ai@​6.0.199

v3.0.198

Compare Source

Patch Changes
  • ai@​6.0.198

v3.0.197

Compare Source

Patch Changes
  • ai@​6.0.197

v3.0.196

Compare Source

Patch Changes
  • ai@​6.0.196

v3.0.195

Compare Source

Patch Changes
  • ai@​6.0.195

v3.0.194

Compare Source

Patch Changes
  • ai@​6.0.194
comarkdown/comark (@​comark/nuxt)

v0.4.0: @​comark/svelte v0.4.0

Compare Source

Bug Fixes
nuxt/eslint (@​nuxt/eslint)

v1.16.0

Compare Source

   🚀 Features
    View changes on GitHub
nuxt/hints (@​nuxt/hints)

v1.1.3

Compare Source

🩹 Fixes
  • Ignore style serialization-only hydration diffs (#​352)
❤️ Contributors
nuxt/scripts (@​nuxt/scripts)

v1.2.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
nuxt/ui (@​nuxt/ui)

v4.8.2

Compare Source

Bug Fixes
  • Form: support setting the name attribute (#​6539) (f8186e2)
  • InputMenu/SelectMenu: re-highlight first item when items change (#​6538) (0414dd0)
  • InputNumber/InputDate/InputTime/Calendar: restore locale prop (#​6546) (ed2f955)
  • module: merge custom variants into AppConfig type (#​6531) (f0571c3)
kane50613/takumi (@​takumi-rs/core)

v1.8.5

Compare Source

Patch Changes

v1.8.4

Compare Source

Patch Changes

v1.8.3

Compare Source

Patch Changes

v1.8.2

Compare Source

Patch Changes

v1.8.1

Compare Source

Patch Changes

v1.8.0

Compare Source

Minor Changes
  • ae2c9aa: Built with nightly Rust toolchain with panic=immediate-abort to reduce binary size
Patch Changes

v1.7.0

Compare Source

Patch Changes
vercel/vercel (@​vercel/functions)

v3.7.1

Compare Source

Patch Changes
  • a7f1f7c: Make ws an optional peer dependency

v3.7.0

Compare Source

Minor Changes
  • 3f3ef14: Add experimental_upgradeWebSocket() API

v3.6.3

Compare Source

Patch Changes

v3.6.2

Compare Source

Patch Changes
vuejs/core (@​vue/compiler-sfc)

v3.5.38

Compare Source

v3.5.37

Compare Source

v3.5.36

Compare Source

Bug Fixes
vuejs/test-utils (@​vue/test-utils)

v2.4.11

Compare Source

compare changes

🩹 Fixes
  • Drop legacy Mutation Event listener entries (#​2844)
  • Handle setData() correctly for components using both setup() and data() (#​2846)
  • Export GlobalMountOptions type (#​2851)
  • Set spec-compliant event.code on keydown/keyup (#​2850)
❤️ Contributors
vercel/ai (ai)

v6.0.204

Compare Source

v6.0.203

Compare Source

Patch Changes
  • f42aa79: fix: harden download URL SSRF guard against hostname and redirect bypasses

    validateDownloadUrl and the file download helpers (downloadBlob, download) could be bypassed in several ways when handling untrusted URLs:

    • A fully-qualified hostname with a trailing dot (e.g. localhost., myhost.local.) skipped the localhost/.local blocklist.
    • IPv6 addresses that embed an IPv4 address in their last 32 bits — IPv4-compatible (::127.0.0.1), IPv4-translated (::ffff:0:127.0.0.1), and NAT64 (64:ff9b::127.0.0.1, including the 64:ff9b:1::/48 local-use prefix) — were not decoded and checked against the private IPv4 ranges.
    • Redirects were validated only after fetch had already followed them, so the request to a redirect target (e.g. an internal/metadata address) had already been issued before the check ran.
    • Several reserved/internal address ranges were not blocked: CGNAT (100.64.0.0/10, used by some cloud providers for internal traffic), benchmarking (198.18.0.0/15), IETF protocol assignments (192.0.0.0/24), the reserved 240.0.0.0/4 block (including the 255.255.255.255 broadcast address), and IPv6 site-local (fec0::/10) and multicast (ff00::/8).

    The validator now strips trailing dots before the hostname checks and fully expands IPv6 addresses to detect embedded private IPv4 targets. The download helpers now follow redirects manually (redirect: 'manual'), re-validating each hop before requesting it, so an unsafe redirect target is never fetched. When a redirect cannot be inspected because the runtime returns an opaque response, the helpers fail closed (reject the redirect) on the server; only in a real browser — where SSRF is not reachable (fetch is constrained by CORS and cannot reach a server's internal network or cloud-metadata endpoints) — is the redirect followed natively so legitimate redirected downloads keep working.

  • 5291f7e: Harden stream text processing and middleware against prototype pollution from stream part IDs.

  • b4b575a: fix: redact server error details from UI message streams by default

    streamText(...).toUIMessageStream() and createUIMessageStream defaulted their onError callback to getErrorMessage, which serializes the raw error (error.toString() / JSON.stringify(error)) into the client-facing { type: 'error', errorText } chunk — and also into tool-output-error parts. The documented default was () => 'An error occurred.', so applications relying on the documented behavior were unknowingly streaming server exception details (internal hostnames, paths, provider request data, validation inputs) to end users.

    The default onError now returns the documented generic 'An error occurred.'. Raw error details are only emitted when the developer explicitly supplies an onError handler. This also redacts tool-output-error and invalid-tool-input error text by default; pass an onError to surface richer messages.

  • Updated dependencies [bfa5864]

  • Updated dependencies [f42aa79]

v6.0.202

Compare Source

Patch Changes
  • 942f2f8: fix(security): re-validate tool approvals from client message history before execution

    The approval-replay path in generateText/streamText reconstructed approved tool calls from the client-supplied messages array and executed them without re-validating input against the tool's schema or re-checking that the tool actually requires approval. A client could forge an assistant message with a pre-approved tool-call part and have the server execute a tool with attacker-chosen arguments.

    The replay path now verifies the HMAC signature (when experimental_toolApprovalSecret is configured), re-validates tool-call input against the tool's input schema, and re-resolves whether the tool requires approval before execution.

  • Updated dependencies [942f2f8]

v6.0.201

Compare Source

Patch Changes
  • 0c8c0ed: fix(ai): return schema-transformed elements in array output mode

    Previously final array output validation checked each element against the schema but returned the raw model output. Array output now returns the validated values so Zod transforms, coercions, defaults, and pipes are applied consistently with object output.

v6.0.200

Compare Source

Patch Changes
  • 14098e7: fix(ai): reject streamText result promises with NoOutputGeneratedError when the model stream ends without producing any output. Previously such streams resolved with an empty step. Incomplete streams with partial output still resolve with the partial result.
  • 2cabe9c: Harden UI message stream processing against prototype pollution from chunk IDs.

v6.0.199

Compare Source

Patch Changes

v6.0.198

Compare Source

Patch Changes

v6.0.197

Compare Source

v6.0.196

Compare Source

Patch Changes

v6.0.195

Compare Source

v6.0.194

Compare Source

WiseLibs/better-sqlite3 (better-sqlite3)

v12.10.1

Compare Source

What's Changed

Full Changelog: WiseLibs/better-sqlite3@v12.10.0...v12.10.1

eslint/eslint (eslint)

v10.5.0

Compare Source

HugoRCD/evlog (evlog)

v2.19.1

Compare Source

What's Changed

Bug Fixes 🐞
Dependency Updates 📦

New Contributors

Full Changelog: https://github.com/HugoRCD/evlog/compare/evlog@2.19.0...evlog@2.19.1

v2.19.0

Compare Source

What's Changed

Features 🚀
Bug Fixes 🐞
Continuous Integration 🔄

New Contributors

Full Changelog: https://github.com/HugoRCD/evlog/compare/evlog@2.18.1...evlog@2.19.0

capricorn86/happy-dom (happy-dom)

v20.10.3

Compare Source

v20.10.2

Compare Source

👷‍♂️ Patch fixes

v20.10.1

Compare Source

v20.10.0

Compare Source

motiondivision/motion-vue (motion-v)

v2.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
nuxt-modules/og-image (nuxt-og-image)

v6.6.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v6.5.3

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v6.5.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
harlan-zw/nuxt-schema-org (nuxt-schema-org)

v6.2.1

Compare Source

No significant changes

    View changes on GitHub

v6.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v6.1.3

[Compare Source](https://r

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 atinux as a code owner June 8, 2026 03:39
@vercel

vercel Bot commented Jun 8, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
nuxt Ready Ready Preview, Comment Jun 15, 2026 8:41am

@socket-security

socket-security Bot commented Jun 10, 2026

Copy link
Copy Markdown

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action Severity Alert  (click "▶" to expand/collapse)
Warn High
Obfuscated code: npm @typescript-eslint/eslint-plugin is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/@nuxt/eslint@1.16.0npm/@typescript-eslint/eslint-plugin@8.61.0

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@typescript-eslint/eslint-plugin@8.61.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm better-sqlite3 is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/better-sqlite3@12.10.1

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/better-sqlite3@12.10.1. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm eslint-plugin-jsdoc is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/@nuxt/eslint@1.16.0npm/eslint-plugin-jsdoc@63.0.2

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/eslint-plugin-jsdoc@63.0.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

Warn High
Obfuscated code: npm happy-dom is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: package.jsonnpm/happy-dom@20.10.3

ℹ Read more on: This package | This alert | What is obfuscated code?

Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev.

Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code.

Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/happy-dom@20.10.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

@renovate

renovate Bot commented Jun 15, 2026

Copy link
Copy Markdown
Contributor Author

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.

@benjamincanac benjamincanac merged commit fa50e85 into main Jun 15, 2026
17 of 18 checks passed
@benjamincanac benjamincanac deleted the renovate/all-minor-patch branch June 15, 2026 09:12
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.

1 participant