From a7b05162da64199e0c489ad4d47a74c8e47fca1b Mon Sep 17 00:00:00 2001 From: Bretton Date: Sat, 15 Aug 2026 16:50:31 -0700 Subject: [PATCH] test(e2e): pin Lemmy 0.19.20, the version we actually verified against MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The e2e image built 0.19.19 while PLAN decision 19 and every task doc name 0.19.20 as the target and strictness ceiling — and the behaviours tasks 13, 14, 15 and 17 were written against were read from 0.19.20's source. So the suite was proving compatibility with a version we had not studied, and the studied version was never exercised. Either half alone is defensible; the pair is not. Suite green on the bump: tests/e2e ok in 267s, no other change required. One note for whoever runs this next: the first attempt failed with Postgres connection-refused from both tidepool-migrate and lemmy, immediately after the Rust rebuild. That is a startup race under a saturated machine, not a version incompatibility — a re-run against the cached image passed untouched. A full Lemmy build from source and `docker compose up` should not be judged on the same pass. Co-Authored-By: Claude Opus 5 (1M context) --- e2e/lemmy/Dockerfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/e2e/lemmy/Dockerfile b/e2e/lemmy/Dockerfile index e426d99..2150ea9 100644 --- a/e2e/lemmy/Dockerfile +++ b/e2e/lemmy/Dockerfile @@ -32,7 +32,7 @@ RUN apt-get update \ # Pin the Lemmy release. lemmy-translations is a git submodule required to # compile (crates/utils embeds it). -ARG LEMMY_VERSION=0.19.19 +ARG LEMMY_VERSION=0.19.20 RUN git clone --depth 1 --branch ${LEMMY_VERSION} https://github.com/LemmyNet/lemmy.git /lemmy \ && cd /lemmy \ && git submodule update --init --recursive --depth 1 -- 2.51.2