From 864682c14d3c9c10ba810927f91343807ba77747 Mon Sep 17 00:00:00 2001 From: "dependabot[bot]" <49699333+dependabot[bot]@users.noreply.github.com> Date: Mon, 31 Aug 2026 21:02:13 +0000 Subject: [PATCH 1/2] build(deps): bump node in the docker group across 1 directory Bumps the docker group with 1 update in the / directory: node. Updates `node` from 26.7.0-trixie-slim to 26.8.1-trixie-slim --- updated-dependencies: - dependency-name: node dependency-version: 26.8.1-trixie-slim dependency-type: direct:production update-type: version-update:semver-minor dependency-group: docker ... Signed-off-by: dependabot[bot] --- Dockerfile | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Dockerfile b/Dockerfile index eb7f1643..d42b291c 100644 --- a/Dockerfile +++ b/Dockerfile @@ -28,7 +28,7 @@ RUN bun install --frozen-lockfile # between whichever ones are present. Every stage here is glibc, so the glibc # package is the one installed and the one loaded; keeping the stages on the # same base is what makes that hold. -FROM node:26.7.0-trixie-slim AS builder +FROM node:26.8.1-trixie-slim AS builder WORKDIR /usr/src/app COPY --from=deps /usr/src/app/node_modules ./node_modules COPY . . @@ -49,7 +49,7 @@ RUN node scripts/copy-monaco.mjs && npx next build # Production image - use Node.js slim for lower memory footprint # trixie-slim: glibc must match the stage where native modules were built (see builder). -FROM node:26.7.0-trixie-slim AS runner +FROM node:26.8.1-trixie-slim AS runner WORKDIR /app ENV NODE_ENV=production From 4e3d4ebe5fa6979bac7175c1d7c97c0c291fd5da Mon Sep 17 00:00:00 2001 From: cevheri Date: Tue, 1 Sep 2026 00:04:15 +0300 Subject: [PATCH 2/2] docs: name the runner image the Dockerfile actually pins Two documents described the Docker runner stage as node:24.16.0-trixie-slim while the Dockerfile had already moved to 26.x, so the sentence a reader trusts for the shipped runtime named a base image that has not been built for some time. Corrected to the pin this change lands, verified by running it: node --version inside the built image reports v26.8.1, and the container answers /api/db/health and /login with 200. --- docs/DISTRIBUTION.md | 2 +- docs/providers/sqlite.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/DISTRIBUTION.md b/docs/DISTRIBUTION.md index cac16b78..531ffc92 100644 --- a/docs/DISTRIBUTION.md +++ b/docs/DISTRIBUTION.md @@ -26,7 +26,7 @@ starting with the first release that includes the release-artifacts workflow — have Docker images only. > **Runtime note:** every channel here runs the production server under Node (`node server.js`), -> including the Docker image — its runner stage is `node:24.16.0-trixie-slim` and `CMD` execs +> including the Docker image — its runner stage is `node:26.8.1-trixie-slim` and `CMD` execs > `node server.js`; Bun is only used to install dependencies during the Docker build and for local > development (`bun dev`). The SQLite DB provider adapts to whichever runtime it finds > (`bun:sqlite` under Bun, `node:sqlite` under Node) — see diff --git a/docs/providers/sqlite.md b/docs/providers/sqlite.md index 75bae33c..c1a9f92b 100644 --- a/docs/providers/sqlite.md +++ b/docs/providers/sqlite.md @@ -51,7 +51,7 @@ for a web-based editor: connect time — see [Runtime & driver selection](#runtime--driver-selection). All packaged distribution channels — the official Docker image, `npx @libredb/studio`, the Homebrew tap, the `.deb`/`.rpm` packages, and the standalone tarballs — run the built app with `node server.js` (the - Docker image's runner stage is `node:24.16.0-trixie-slim`; the other channels bundle their own pinned + Docker image's runner stage is `node:26.8.1-trixie-slim`; the other channels bundle their own pinned Node 24 runtime), so they all use `node:sqlite`. `bun:sqlite` is used for local development (`bun dev`) and the test suite, where Next.js runs directly under Bun. Only on a runtime with neither driver does `connect()` throw a `DatabaseConfigError`.