Skip to content

The agent that grows with you

chore: update base debian images to 2026-10-20

Maciej Lisiewskic73cbcc4cbbd
diff --git a/.github/workflows/remote-backends.yml b/.github/workflows/remote-backends.yml
index f653b06b869..e0315bde22e 100644
--- a/.github/workflows/remote-backends.yml
+++ b/.github/workflows/remote-backends.yml
@@ -31,7 +31,7 @@ concurrency:
env:
# One small image for both the sshd host and the docker backend's sandbox, pinned
# by digest so a tag move cannot change what the lane tests.
- HERMES_TEST_IMAGE_REF: debian:13-slim@sha256:a29215f6a35e51e22adffa17f89e9d2ef06214e64a2bad10d765c46aea49f11f
+ HERMES_TEST_IMAGE_REF: debian:trixie-20261020-slim@sha256:62bd423aeee912639ca8ee681c2b762cb3e25137e0a92b20be455898a9f034ad
jobs:
real-backends:
diff --git a/Dockerfile b/Dockerfile
index e3d11031c8d..71d4be50fe9 100644
--- a/Dockerfile
+++ b/Dockerfile
@@ -4,7 +4,8 @@
# See #70480 and https://sqlite.org/wal.html#walresetbug.
# Pinned by the multi-arch index digest: uv and node already come from pm's
# sha-verified lock, and a tag alone would let the base drift under them.
-FROM debian:13.4@sha256:e2d08da6f42ef4b09b165d55528a12727aeed8240dc9edf888e3ec07e10ef9da AS sqlite_build
+
+FROM debian:trixie-20261020@sha256:4c25275446ca371766b8b093c696782eabce06263fccacb8d5d813b3dc44b308 AS sqlite_build
ARG SQLITE_AUTOCONF_VERSION=3530400
ARG SQLITE_SHA256=0e9483900e92cd5de8fd48d16bf9200145a61f7fd5be542a5ac81d8a9516eb9c
RUN apt-get -o Acquire::Retries=3 update && \
@@ -43,7 +44,7 @@ RUN apt-get -o Acquire::Retries=3 update && \
make install
# Same digest as sqlite_build: the built libsqlite must match this libc.
-FROM debian:13.4@sha256:e2d08da6f42ef4b09b165d55528a12727aeed8240dc9edf888e3ec07e10ef9da AS runtime_base
+FROM debian:trixie-20261020@sha256:4c25275446ca371766b8b093c696782eabce06263fccacb8d5d813b3dc44b308 AS runtime_base
# Disable Python stdout buffering to ensure logs are printed immediately.
# Do not write .pyc files at runtime: /opt/hermes is immutable in the