chore(deps): update dependency @nextcloud/vite-config to ^1.7.2 (stable32)

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
@nextcloud/vite-config	^1.6.0 -> ^1.7.2

---

Release Notes

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

v1.7.2

Compare Source

Fixed

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

Changed

• Updated development dependencies
• chore(deps): Bump @​vitejs/plugin-vue2 to 2.3.4 #​727

v1.7.1

Compare Source

Fixed

• fix: make configuration rolldown compatible #​718

Changed

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

v1.7.0

Compare Source

Added

• Minimum Vite version is now v7.1.4

Changed

• fix: bump vite version to fix running in watch mode #​694
• [stable1] chore(deps): update dependencies by @​susnux in nextcloud-libraries#695
• chore: prepare v1.7.0 by @​susnux in nextcloud-libraries#697

Full Changelog: nextcloud-libraries/nextcloud-vite-config@v1.6.0...v1.7.0

---

Configuration

📅 Schedule: Branch creation - "every weekend" in timezone Europe/Berlin, 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.

🔕 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: [email protected]
npm error Found: [email protected]
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/[email protected]
npm error node_modules/@nextcloud/vite-config
npm error   dev @nextcloud/vite-config@"^1.7.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/2025-10-23T22_36_03_936Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-10-23T22_36_03_936Z-debug-0.log

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 59.51%. Comparing base (cd514f7) to head (65040e9).
⚠️ Report is 4 commits behind head on stable32.

Additional details and impacted files

@@             Coverage Diff              @@
##           stable32    #7850      +/-   ##
============================================
- Coverage     59.73%   59.51%   -0.23%     
============================================
  Files           499      307     -192     
  Lines         38416    38226     -190     
  Branches       1061      869     -192     
============================================
- Hits          22948    22750     -198     
- Misses        15362    15370       +8     
  Partials        106      106              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.