chore(deps): bump @nextcloud/vite-config from 2.4.0 to ^2.5.2

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@nextcloud/vite-config	^2.4.0 → ^2.5.2

---

Release Notes

nextcloud/nextcloud-vite-config (@​nextcloud/vite-config)

v2.5.2

Compare Source

🐛 Fixed bugs

• fix(REUSE): also add correct license headers for facade chunks #​736 (susnux)

Other changes

• Updated development dependencies

v2.5.1

Compare Source

🐛 Fixed bugs

• fix: make configuration rolldown compatible #​717 (susnux)

Other changes

• chore(deps): Bump rollup-plugin-node-externals to 8.1.1
• chore(deps): Bump magic-string to 0.30.19

v2.5.0

Compare Source

Added

• Minimum Vite version is now 7.1.4

🐛 Fixed bugs

• fix: bump vite version to fix running in watch mode #​693 (susnux)

Other changes

• chore: update vite-plugin-node-polyfills to 0.24.0 #​678 (skjnldsv)
• chore: various dev deps upgrades #​680 (skjnldsv)
• chore(deps): Bump @​vitejs/plugin-vue from 6.0.0 to 6.0.1 #​681
• chore(deps): Bump cipher-base from 1.0.4 to 1.0.6 #​687
• chore(deps): Bump sha.js from 2.4.11 to 2.4.12 #​688
• chore(deps): Bump magic-string from 0.30.17 to 0.30.18 #​691
• chore(deps): Bump rollup-plugin-node-externals from 8.0.1 to 8.1.0 #​690

---

Configuration

📅 Schedule: (in timezone Europe/Berlin)

• Branch creation
  • Between 12:00 AM and 03:59 AM, on day 1 of the month (* 0-3 1 * *)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: @nextcloud/timezones@1.0.2
npm error Found: vite@6.4.2
npm error node_modules/vite
npm error   dev vite@"^6.4.1" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^7.1.10" from @nextcloud/vite-config@2.5.2
npm error node_modules/@nextcloud/vite-config
npm error   dev @nextcloud/vite-config@"^2.5.2" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-05-18T10_45_50_960Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-05-18T10_45_50_960Z-debug-0.log