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

@renovate renovate Bot commented Jun 9, 2025

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
@nuxt/eslint (source) 1.4.11.16.0 age confidence dependencies minor
@nuxt/scripts (source) 1.1.01.2.1 age confidence dependencies minor
@playwright/test (source) 1.60.01.61.0 age confidence devDependencies minor
@vue/test-utils 2.4.62.4.11 age confidence devDependencies patch
@vueuse/nuxt (source) 14.0.014.3.0 age confidence dependencies minor
danielroe/provenance-action v0.1.0v0.1.1 age confidence action patch
mcr.microsoft.com/playwright v1.60.0-noblev1.61.0-noble age confidence container minor
nuxt-og-image (source) 5.1.45.1.13 age confidence dependencies patch
pnpm (source) 11.1.211.8.0 age confidence packageManager minor
simple-git-hooks 2.13.02.13.1 age confidence devDependencies patch
unplugin-vue-router (source) ^0.12.0^0.19.0 age confidence dependencies minor
vue-sonner 2.0.02.0.9 age confidence dependencies patch
vue-tsc (source) 3.0.13.3.5 age confidence devDependencies minor

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

nuxt/eslint (@​nuxt/eslint)

v1.16.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.15.2

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.15.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.15.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.14.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.13.0

Compare Source

   🚀 Features
  • Upgrade eslint-flat-config-utils eslint-plugin-import-lite and eslint-plugin-jsdoc  -  by @​antfu (10bf9)
    View changes on GitHub

v1.12.1

Compare Source

No significant changes

    View changes on GitHub

v1.11.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.10.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.9.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v1.8.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.7.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.7.0

Compare Source

   🚀 Features
    View changes on GitHub

v1.6.0

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.2

Compare Source

   🚀 Features
    View changes on GitHub

v1.5.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub

v1.5.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub
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

v1.1.1

Compare Source

   🐞 Bug Fixes
    View changes on GitHub
microsoft/playwright (@​playwright/test)

v1.61.0

Compare Source

🔑 WebAuthn passkeys

New Credentials virtual authenticator, available via browserContext.credentials, lets tests register passkeys and answer navigator.credentials.create() / navigator.credentials.get() ceremonies in the page — no real hardware key required, works in all browsers:

const context = await browser.newContext();

// Seed a passkey your backend provisioned for a test user.
await context.credentials.create('example.com', {
  id: credentialId,
  userHandle,
  privateKey,
  publicKey,
});
await context.credentials.install();

const page = await context.newPage();
await page.goto('https://example.com/login');
// The page's navigator.credentials.get() is answered with the seeded passkey.

You can also let the app register a passkey once in a setup test, read it back with credentials.get(), and seed it into later tests — see Credentials for details.

🗃️ Web Storage

New WebStorage API, available via page.localStorage and page.sessionStorage, reads and writes the page's storage for the current origin:

await page.localStorage.setItem('token', 'abc');
const token = await page.localStorage.getItem('token');
const items = await page.sessionStorage.items();
New APIs
Network
Browser and Screencast
  • New option artifactsDir in browserType.connectOverCDP() controls where artifacts such as traces and downloads are stored when attached to an existing browser.
  • New option cursor in screencast.showActions() controls the cursor decoration rendered for pointer actions.
  • The onFrame callback in screencast.start() now receives a timestamp of when the frame was presented by the browser.
Test runner
  • The testOptions.video option now supports the same set of modes as trace: new 'on-all-retries', 'retain-on-first-failure' and 'retain-on-failure-and-retries' values. See the video modes table for which runs are recorded and kept in each mode.
  • Supported expect.soft.poll(...).
  • New fullConfig.argv — a snapshot of process.argv from the runner process, handy for reading custom arguments passed after the -- separator.
  • New fullConfig.failOnFlakyTests mirrors the config option, so reporters can explain why a flaky run failed.
  • testInfo.errors now lists each sub-error of an AggregateError as a separate entry.
  • New -G command line shorthand for --grep-invert.
🛠️ Other improvements
  • Playwright now supports Ubuntu 26.04.
  • HAR and trace recordings now include WebSocket requests.
Browser Versions
  • Chromium 149.0.7827.55
  • Mozilla Firefox 151.0
  • WebKit 26.5

This version was also tested against the following stable channels:

  • Google Chrome 149
  • Microsoft Edge 149
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

v2.4.10

Compare Source

v2.4.9

Compare Source

compare changes

🩹 Fixes
  • Tolerate duplicate attachTo cleanup (#​2830)
📖 Documentation
🏡 Chore
  • Migrate renovate config (5d37934)
🤖 CI
  • Pin github actions to commit hashes (75dcef3)
❤️ Contributors

v2.4.8

Compare Source

compare changes

🩹 Fixes
  • Correct declaration entrypoint (#​2826)
🤖 CI
❤️ Contributors

v2.4.7

Compare Source

compare changes

🚀 Enhancements
  • Add Chinese docs translation (#​2552)
  • SetData()/shallowMount with initialData for components using the Composition API / <script setup> (#​2655)
🩹 Fixes
  • Preserve code from keyboard events (#​2434)
  • Switch browser and require exports definitions (#​2501)
  • Re-add peer dependencies but with wider range (#​2511)
  • Resolve warnings in docs:dev (30b7491)
  • Resolve TypeScript type errors in .vitepress/config (#​2549)
  • Accept FunctionalComponent as selector (0bb947f)
  • Text() misses content for array functional component (#​2579)
  • Use await in test (c5482b4)
  • deps: Update dependency vue-component-type-helpers to v3 (#​2683)
  • Remove wrapper div when unmount (#​2700)
  • Make mount options slots compatible with noUncheckedIndexedAccess true (#​2713)
  • Add missing peerDependency @​vue/compiler-dom (75801ba)
  • docs: Declare css module for vitepress typecheck (ddaca97)
💅 Refactors
  • Enforce consistent usage of type imports (#​2734)
📖 Documentation
  • Clarify findComponent vs getComponent (#​2435)
  • Update fr docs (67064ef)
  • Add note about partial transition stub support (#​2431)
  • Fix missing data at passing data section essentials guide (dda205e)
  • Fix missing data at passing data section essentials guide fr (ae2c72c)
  • Fix plugin TS declaration example (#​2466)
  • Fixed incorrect checkbox value check (#​2495)
  • Capital letter in sentence fix (#​2499)
  • Import missing DOMWrapper on Implementation of the plugin section (#​2519)
  • Add migration step for deprecated ref syntax in findAllComponents (#​2498)
  • Correct anchor hash links and fix typo (#​2551)
  • Center logo on home (#​2559)
  • zh-cn: Review a-crash-course (#​2563)
  • Use code-group for install commands (#​2571)
  • zh-cn: Review event-handing.md (#​2572)
  • zh-cn: Enhance conditional-rendering.md (#​2562)
  • zh-cn: Review easy-to-test (#​2567)
  • zh-cn: Review passing-data.md (#​2575)
  • zh-cn: Review async-suspense.md (#​2576)
  • zh: 优化 API 文档格式和内容 (#​2569)
  • zh: 更新 Vitest 模拟日期和计时器的说明 (#​2578)
  • zh-cn: Review http-requests.md (#​2580)
  • zh-cn: Review forms (#​2582)
  • zh-cn: Guide/advanced/slots.md (#​2565)
  • zh: Review extending-vtu (#​2583)
  • zh: Review index (#​2584)
  • Fix modelValue test example (85bfdf4)
  • Removes broken link from plugins.md (69bc1ce)
  • zh: Review transitions, component-instance, and reusability-composition (#​2616)
  • zh: Review v-model and vuex (#​2617)
  • zh: Review all the rest advanced guide (#​2619)
  • zh: Review migration (#​2623)
  • Fix a typo in transitions.md (#​2635)
  • Update crash-course to script setup (c81aa79)
  • Update Essentials section to setup (composition api) (#​2647)
  • Typos in examples (#​2678)
  • Typo in easy-to-test.md (#​2710)
  • Add note about mocking requestAnimationFrame for transitions (2324c65)
  • Updated example TodoApp to script setup (#​2727)
  • Remove "Using data" section from "Conditional Rendering" guide and fix passing data test example (#​2743)
  • Follow-up fixes for the conditional rendering guide (#​2744)
  • Mention shallowMount stub name changes in migration guide (80e051a)
  • Update conditional rendering documentation to clarify isVisible() usage with attachTo (#​2799)
  • Restore Options API component for data() mounting example (#​2804)
  • Promote Vitest as recommended test runner (#​2805)
  • api: Note that setValue does not accept objects on <select> (#​2819)
🏡 Chore
  • Add api/index.md to docs:translation:compare (6b8681c)
  • Remove unnecessary generic arguments (cfd70c6)
  • Ignore TS error in config object (9d0a618)
  • Simplify eslint packages (c1d0ffd)
  • Use eslint v9 with flat config (2f19fdf)
  • Expose Stubs type publicly (#​2492)
  • Update documentation file path (9c96594)
  • Use pnpm v10 (e4c2cb3)
  • Pnpm approve build (81c54e9)
  • Use github issue forms (#​2673)
  • Exclude class components from test type-checking (0899008)
  • Add explicit coverage include for vitest v4 (51672b9)
  • Update to prettier v3.7 (fed9e7c)
  • Migrate to oxfmt (81c1de9)
  • Migrate to oxlint (a361908)
  • Prepare TypeScript 6 migration settings (55e1262)
  • Adjust tsd config for TypeScript 6 (7d23eb5)
  • Avoid TypeScript 6 target deprecation warning (81d063c)
🤖 CI
  • Remove node v22 build (7ebf58d)
  • Add node v22 build (57540ee)
  • Use "pool: threads" instead of vmThreads (d0cbb54)
  • Remove node v18 and add v24 (fd9cf95)
  • Add trusted publishing release workflow (#​2825)
❤️ Contributors
vueuse/vueuse (@​vueuse/nuxt)

v14.3.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
   🏎 Performance
    View changes on GitHub

v14.2.1

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v14.2.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
    View changes on GitHub

v14.1.0

Compare Source

   🚀 Features
   🐞 Bug Fixes
  • Typescript type of isIOS constant  -  by @​toofishes in [#​5163]

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.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 9, 2025

Copy link
Copy Markdown

Deploying dev-mode with  Cloudflare Pages  Cloudflare Pages

Latest commit: a6593b8
Status: ✅  Deploy successful!
Preview URL: https://b4871a9a.dev-mode.pages.dev
Branch Preview URL: https://renovate-all-minor-patch.dev-mode.pages.dev

View logs

@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 11 times, most recently from a0e4601 to 3853611 Compare June 16, 2025 08:36
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 16 times, most recently from 5d5db8c to 1a5208b Compare June 22, 2025 23:38
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 21 times, most recently from 6b58693 to 33dfcc0 Compare July 6, 2025 14:50
@renovate renovate Bot force-pushed the renovate/all-minor-patch branch 6 times, most recently from fc47a1c to 12a7b8e Compare July 8, 2025 00:37
@socket-security

socket-security Bot commented Nov 5, 2025

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.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/@typescript-eslint/eslint-plugin@8.61.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.6

ℹ 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.6. 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 execa is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/nuxt-og-image@5.1.13npm/execa@9.6.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/execa@9.6.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 js-yaml is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/eslint@9.39.4npm/@nuxt/eslint@1.16.0npm/js-yaml@4.2.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/js-yaml@4.2.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 satori is 90.0% likely obfuscated

Confidence: 0.90

Location: Package overview

From: pnpm-lock.yamlnpm/nuxt-og-image@5.1.13npm/satori@0.18.4

ℹ 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/satori@0.18.4. 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

@socket-security

socket-security Bot commented Jun 16, 2026

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants