chore(deps): lock file maintenance

[renovate]

This PR contains the following updates:

Update	Change
lockFileMaintenance	All locks refreshed

🔧 This Pull Request updates lock files to use the latest dependency versions.

---

Configuration

📅 Schedule: (in timezone Europe/Paris)

• 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.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​shikijs/​types@​4.4.2
	happy-dom@​20.11.2
	@​tanstack/​vue-virtual@​3.13.35
	@​tiptap/​extension-placeholder@​3.29.2
	@​tiptap/​extension-node-range@​3.29.2
	@​ai-sdk/​gateway@​4.0.46
	@​tiptap/​pm@​3.29.2
	@​vueuse/​shared@​14.4.0
	@​ai-sdk/​vue@​4.0.58
	@​tiptap/​extension-text-align@​3.29.2
	@​tiptap/​extension-horizontal-rule@​3.29.2
	@​inertiajs/​vue3@​3.6.1
	@​tiptap/​extension-code@​3.29.2
	@​tiptap/​starter-kit@​3.29.2
	@​tiptap/​extension-image@​3.29.2
	@​vueuse/​core@​14.4.0
	@​tiptap/​extension-collaboration@​3.29.2
	@​tiptap/​extension-mention@​3.29.2
	@​iconify-json/​logos@​1.2.12
	@​iconify-json/​simple-icons@​1.2.93
	@​tiptap/​extension-emoji@​3.29.2
	@​tiptap/​extension-floating-menu@​3.29.2
	@​tiptap/​extension-bubble-menu@​3.29.2
	shiki@​4.4.2
	@​nuxt/​eslint-config@​1.17.0
	@​tiptap/​extension-drag-handle-vue-3@​3.29.2
	@​ai-sdk/​anthropic@​4.0.36
	@​tiptap/​suggestion@​3.29.2
	@​tiptap/​vue-3@​3.29.2
	@​tiptap/​extension-drag-handle@​3.29.2
	@​tiptap/​markdown@​3.29.2
	@​takumi-rs/​core@​2.5.11
	@​iconify-json/​lucide@​1.2.122
See 24 more rows in the dashboard

View full report

[socket-security]

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		Potentially malicious package (AI signal): npm @ghostery/adblocker-content is 60.0% likely malicious Notes: This module is security-sensitive: it continuously observes a live document for newly seen ids/classes/hrefs and reports them via a callback, and it also provides a generic ability to execute arbitrary JavaScript supplied as s in the page context (with immediate self-removal to reduce traces). While this code does not itself show network exfiltration, the injection primitive and fingerprint-like DOM feature reporting make it high-risk if s or cb are not strictly trusted and controlled. Confidence: 0.60 Severity: 0.90 From: pnpm-lock.yaml → npm/capture-website@5.1.0 → npm/@ghostery/adblocker-content@2.18.2 ℹ Read more on: This package | This alert | What is AI-detected potential malware? 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: Given the AI system's identification of this package as malware, extreme caution is advised. It is recommended to avoid downloading or installing this package until the threat is confirmed or flagged as a false positive. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/@ghostery/adblocker-content@2.18.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		Obfuscated code: npm yargs is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: pnpm-lock.yaml → npm/capture-website@5.1.0 → npm/yargs@17.7.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/yargs@17.7.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