fix(deps): update dependency better-sqlite3 to ^12.5.0

[homarr-renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
better-sqlite3	^12.4.1 -> ^12.5.0

---

Release Notes

WiseLibs/better-sqlite3 (better-sqlite3)

v12.5.0

Compare Source

What's Changed

• Update SQLite to version 3.51.1 in #​1424

Full Changelog: WiseLibs/better-sqlite3@v12.4.6...v12.5.0

v12.4.6

Compare Source

What's Changed

• Fix npm publishing by @​mceachen in #​1423

Full Changelog: WiseLibs/better-sqlite3@v12.4.5...v12.4.6

v12.4.5

Compare Source

What's Changed

• Add support for Node v25 and Electron 39+ prebuilds by @​mceachen in #​1422

Full Changelog: WiseLibs/better-sqlite3@v12.4.4...v12.4.5

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), 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 has been generated by Renovate Bot.

[homarr-approvals]

Automatically approved by GitHub Action

[deepsource-io]

Here's the code health analysis summary for commits 069ed0a..7271344. View details on DeepSource ↗.

Analysis Summary

Analyzer	Status	Summary	Link
JavaScript	✅ Success		View Check ↗

---

💡 If you’re a repository administrator, you can configure the quality gates from the settings.

[homarr-approvals]

Automatically approved by GitHub Action

[homarr-approvals]

Automatically approved by GitHub Action

[homarr-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: pnpm-lock.yaml

Scope: all 44 workspace projects
Progress: resolved 1, reused 0, downloaded 0, added 0
Progress: resolved 63, reused 0, downloaded 0, added 0
Progress: resolved 77, reused 0, downloaded 0, added 0
Progress: resolved 127, reused 0, downloaded 0, added 0
Progress: resolved 138, reused 0, downloaded 0, added 0
Progress: resolved 172, reused 0, downloaded 0, added 0
Progress: resolved 179, reused 0, downloaded 0, added 0
Progress: resolved 291, reused 0, downloaded 0, added 0
/tmp/renovate/repos/github/homarr-labs/homarr/apps/nextjs:
 ERR_PNPM_NO_MATCHING_VERSION  No matching version found for @next/env@16.0.7 published by Mon Dec 01 2025 01:45:08 GMT+0000 (Coordinated Universal Time) while fetching it from https://registry.npmjs.org/. Version 16.0.7 satisfies the specs but was released at Wed Dec 03 2025 15:16:25 GMT+0000 (Coordinated Universal Time)

This error happened while installing the dependencies of next@16.0.7

The latest release of @next/env is "16.0.7". Published at 12/3/2025 3:16:25 PM

Other releases are:
  * next-11: 11.1.4 published at 1/27/2022
  * next-12-2-6: 12.2.6 published at 9/29/2022
  * next-14-1: 14.1.1 published at 2/29/2024
  * rc: 15.0.0-rc.1 published at 10/15/2024
  * next-13: 13.5.11 published at 3/27/2025
  * next-12-3-2: 12.3.7 published at 3/28/2025
  * next-14: 14.2.33 published at 9/23/2025
  * beta: 16.0.0-beta.0 published at 10/10/2025
  * backport: 15.4.8 published at 12/3/2025 3:35:32 PM
  * next-15-0: 15.1.9 published at 12/3/2025 4:08:18 PM
  * next-15-0-0: 15.0.5 published at 12/3/2025 4:10:53 PM
  * next-15-3: 15.3.6 published at 12/3/2025 4:11:36 PM
  * next-15-2: 15.2.6 published at 12/3/2025 4:29:43 PM
  * canary: 16.1.0-canary.13 published at 12/3/2025 11:32:16 PM

If you need the full list of all 2554 published versions run "$ pnpm view @next/env versions".

If you want to install the matched version ignoring the time it was published, you can add the package name to the minimumReleaseAgeExclude setting. Read more about it: https://pnpm.io/settings#minimumreleaseageexclude

[homarr-approvals]

Automatically approved by GitHub Action