chore(deps)(deps): bump better-sqlite3 from 12.11.1 to 13.0.1

[dependabot]

Bumps better-sqlite3 from 12.11.1 to 13.0.1.

Release notes

Sourced from better-sqlite3's releases.

v13.0.1

Full Changelog: WiseLibs/better-sqlite3@v13.0.0...v13.0.1

Fixed a regression in parameter binding where it would be overly strict and reject plain objects from other realms (e.g., in jest tests).

v13.0.0

Version 13.0.0 marks a major milestone, as it's the first version of better-sqlite3 to run on the N-API. This means prebuilt binaries should theoretically work across different versions of Node.js and Electron, and perhaps even other runtimes like Bun. As a result, we've removed the deprecated prebuild-install dependency, and now prebuilt binaries are published directly with the better-sqlite3 code itself. If your platform/architecture doesn't have a prebuilt binary, it should compile during install as before.

What's Changed

• Refactored codebase to use node-addon-api by @​JoshuaWise in WiseLibs/better-sqlite3#1498
• Added a new db.explain() method, for running EXPLAIN queries without needing to supply bound parameters.
• Added a new preparedStatement.toString() method, for getting the expanded SQL of a prepared statement.
• Fix SqliteError cross-realm and Error.isError compatibility by @​dennismutuku2005 in WiseLibs/better-sqlite3#1473

New Contributors

• @​dennismutuku2005 made their first contribution in WiseLibs/better-sqlite3#1473

Full Changelog: WiseLibs/better-sqlite3@v12.12.0...v13.0.0

v12.12.0

What's Changed

[!WARNING]

BREAKING: Starting with Electron v43, binary assets will require glibc 2.41 or higher on Linux hosts.

• Update SQLite to version 3.53.3 by @​JoshuaWise in WiseLibs/better-sqlite3#1492
• Utilize node:20-trixie for Electron v43 and onwards by @​neoxpert in WiseLibs/better-sqlite3#1495

Full Changelog: WiseLibs/better-sqlite3@v12.11.2...v12.12.0

v12.11.2

What's Changed

• Add support for electron v43 prebuilds by @​m4heshd in WiseLibs/better-sqlite3#1490

Full Changelog: WiseLibs/better-sqlite3@v12.11.1...v12.11.2

Commits

• 6efdbc5 13.0.1
• 32ee0ab Merge remote-tracking branch 'origin/master'
• bce8300 fixed overly strict regression in parameter binding
• ecfe2f7 13.0.0
• ae19080 fixed typos
• 57d4bbb implemented Database#explain()
• 49fd7e6 added docs for Statement#toString()
• 1cb18ec implemented Statement#toString()
• af60f6b updated github workflow dep versions
• 6ffd750 fixed tests for SqliteError
• Additional commits viewable in compare view

Install script changes

This version modifies install script that runs during installation. Review the package contents before updating.

[github-actions]

📊 Coverage Report

Metric		PR	Base	Diff
Statements	████████████████████	2070/2070 (100%)	2070/2070 (100%)	⚪ 0%
Branches	████████████████████	279/279 (100%)	279/279 (100%)	⚪ 0%
Functions	████████████████████	88/88 (100%)	88/88 (100%)	⚪ 0%
Lines	████████████████████	2070/2070 (100%)	2070/2070 (100%)	⚪ 0%

---

_{Updated for 20299df | Compared against base branch}

[github-actions]

⏱️ Performance Report

✅ Tests	135 passed, 0 failed, 0 skipped
🧪 Suites	32
⏱️ Total step time	247.00s 🔴 +56.00s
⚙️ Test execution	239.47s 🔴 +53.12s

🐢 Slowest test suites

#	Suite	Tests	Duration	vs Base
1	PostgresWakeListener	17	27.13s	🔴 +5.64s
2	runWorkerLoop	13	21.03s	🔴 +4.65s
3	OutboxClaimer (publish outcomes)	9	14.99s	🔴 +2.94s
4	WakeSocketServer + WakeSocketClient	9	14.53s	🔴 +3.10s
5	KafkaInboxConsumer	8	13.14s	🔴 +3.34s
6	SqliteOutboxStore	8	13.06s	🔴 +3.03s
7	OutboxWaker	7	11.76s	🔴 +2.87s
8	MysqlOutboxStore	7	11.00s	🔴 +2.50s
9	InProcessOutboxTransport	5	8.09s	🔴 +2.24s
10	SqliteInboxStore	5	7.97s	🔴 +1.82s

🐌 Slowest individual tests

#	Suite	Test	Duration	vs Base
1	PostgresOutboxStore wakeChannel	PostgresOutboxStore wakeChannel enqueue fires pg_notify on the configured channel (observed via LISTEN)	3.26s	🔴 +808ms
2	OutboxProducer (atomic enqueue)	OutboxProducer (atomic enqueue) enqueue commits the outbox row with the business write	2.57s	🔴 +718ms
3	OutboxProducer (atomic enqueue)	OutboxProducer (atomic enqueue) a throw rolls back BOTH the outbox row and the business write	1.94s	🔴 +437ms
4	OutboxClaimer (publish outcomes)	OutboxClaimer (publish outcomes) tick publishes a pending row and marks it completed	1.86s	🔴 +442ms
5	OutboxClaimer (publish outcomes)	OutboxClaimer (publish outcomes) a RetryableError without delay reschedules with backoff	1.83s	🔴 +442ms
6	OutboxWaker	OutboxWaker wait() returns immediately when the signal is already aborted	1.80s	🔴 +495ms
7	PostgresOutboxStore	PostgresOutboxStore claimBatch claims due rows; empty when none due; reclaims stuck	1.79s	🔴 +612ms
8	OutboxWaker	OutboxWaker notify() with a signal present still cleans up the abort listener	1.77s	🔴 +440ms
9	OutboxWaker	OutboxWaker a notify() with no waiter is latched and consumed by the next wait	1.76s	🔴 +587ms
10	KafkaOutboxTransport	KafkaOutboxTransport falls back to id as the key and defaults the prefix to empty	1.76s	🔴 +617ms
11	DI tokens	DI tokens tokens are global Symbol.for registrations under the package namespace	1.76s	🔴 +381ms
12	runWorkerLoop	runWorkerLoop a waker-driven loop still stops promptly on abort (waker path honours the signal)	1.75s	🔴 +297ms
13	SqliteOutboxStore	SqliteOutboxStore claimBatch does NOT reclaim a freshly claimed processing row	1.74s	🔴 +410ms
14	postgres schema	postgres schema inbox_events: composite unique index	1.74s	🔴 +295ms
15	PostgresWakeListener	PostgresWakeListener an error while closing the old connection is reported, and the loop survives	1.74s	🔴 +473ms

---

_{Updated for 20299df | Compared against base branch}

[github-actions]

🧠 Cognitive Complexity Report

Metric	PR	Base	Diff
Total complexity	79	79	⚪ 0
Max function complexity	12	12	⚪ 0
Functions measured	39	39	⚪ 0

🧩 Most complex functions

Function	Location	Complexity	Status
runWorkerLoop	packages/messaging/outbox-worker.ts:34	12	🟢 OK
KafkaInboxConsumer.consume	packages/messaging/adapters/kafka/kafka-inbox-consumer.ts:67	5	🟢 OK
PostgresWakeListener.#supervise	packages/messaging/dialects/postgres/wake.ts:122	5	🟢 OK
WakeSocketServer.listen	packages/messaging/wake-socket.ts:52	5	🟢 OK
OutboxClaimer.onPublishError	packages/messaging/outbox-claimer.service.ts:84	4	🟢 OK
deriveDedupKey	packages/messaging/wire-contract.ts:55	4	🟢 OK
MysqlInboxStore.runOnce	packages/messaging/dialects/mysql/inbox-store.ts:43	3	🟢 OK
PostgresInboxStore.runOnce	packages/messaging/dialects/postgres/inbox-store.ts:37	3	🟢 OK
SqliteInboxStore.runOnce	packages/messaging/dialects/sqlite/inbox-store.ts:39	3	🟢 OK
KafkaInboxConsumer.readKey	packages/messaging/adapters/kafka/kafka-inbox-consumer.ts:90	2	🟢 OK

🧭 Cognitive complexity is reported as a review signal, not a merge gate. Prefer small, intention-revealing refactors when complexity rises.

---

_{Updated for 20299df | Compared against base branch}

[rodrigobnogueira]

Closing per the isolated better-sqlite3 major review in #32 (released as 0.5.1).

The peer range now accepts better-sqlite3 13 (^11 || ^12 || ^13), so consumers on Node 22+ can upgrade freely. This PR is different: it bumps the devDependency, and better-sqlite3 13 requires Node >=22 while this package still supports Node >=20. That is precisely why the "Package tests/coverage (Node 20)" job fails here — merging it would silently drop a supported Node.

The rule is now recorded in the guidelines: peer majors are widened, never swapped — the devDependency stays on the newest major that still installs on the oldest supported Node, and a dedicated CI leg (better-sqlite3 13 compatibility (Node 22)) exercises the newest supported major so both ends of the range stay tested.

Reopen this when the support line moves to Node >=22.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.