Skip to content

build(deps): bump node from 26.7.0-trixie-slim to 26.8.1-trixie-slim in the docker group across 1 directory #529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
cevheri merged 2 commits into from
Aug 31, 2026
+4 −4
Merged

build(deps): bump node from 26.7.0-trixie-slim to 26.8.1-trixie-slim in the docker group across 1 directory #529

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
864682c
build(deps): bump node in the docker group across 1 directory
dependabot[bot] Aug 31, 2026
4e3d4eb
docs: name the runner image the Dockerfile actually pins
cevheri Aug 31, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions Dockerfile
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 . .
Expand All @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/DISTRIBUTION.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down
2 changes: 1 addition & 1 deletion docs/providers/sqlite.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`.
Expand Down
Loading