⚠️ Use this release, not
0.10.3. The0.10.3container image does not start: its
sqlite3native binary was built against glibc 2.38 while the runtime image (node:22-slim,
Debian bookworm) provides 2.36, so the driver failed to load and the app could not reach its
database. The release gate caught it on both architectures and the GitHub release was never
published, but the image had already been pushed.0.10.4contains the same features and
fixes as0.10.3plus the correction below.
Fixed
- The container image starts again.
sqlite3stays on the5.xline, whose prebuilt
binaries match the Debian bookworm runtime, instead of the6.xline whose prebuilds require
a newer glibc than the base image provides. The dependency advisories that motivated the
original bump are still resolved —node-gypandtarare pinned forward throughoverrides
so the vulnerabletarnever enters the tree, leavingnpm auditclean without changing the
driver. Verified by building the production image and booting it, not only by the test suite.