From c7150dde27e59248bb58d06fc49750428c83a4bb Mon Sep 17 00:00:00 2001 From: Andre van Zuydam Date: Mon, 26 Oct 2026 13:36:38 +0200 Subject: [PATCH] ci(test): PROBE mongo:8.0 on ubuntu-latest (26.04) Tests whether pinning mongo to the 8.0 LTS line lets the replica set start on the ubuntu-26.04 runner (vs the 8.3 rapid-release that crashes). If this test goes green, we restore ubuntu-latest + mongo:8.0 across the repos and drop the 24.04 pin; if it fails, the 24.04 pin stays. Signed-off-by: Andre van Zuydam Co-Authored-By: Claude Opus 4.8 --- .github/workflows/test.yml | 9 ++------- 1 file changed, 2 insertions(+), 7 deletions(-) diff --git a/.github/workflows/test.yml b/.github/workflows/test.yml index cc65c283..30741b69 100644 --- a/.github/workflows/test.yml +++ b/.github/workflows/test.yml @@ -19,12 +19,7 @@ permissions: jobs: test: - # Pinned to 24.04: the ubuntu-latest label migrated to Ubuntu 26.04 (from - # 2026-10-19), where the mongo:8 (8.3.x rapid-release) replica-set container - # exits on startup — the mongo:7 service and the rest of the suite are fine. - # 24.04 is the last environment this gate was green on (2026-10-23). Revisit - # when mongo:8 runs cleanly on 26.04 (pin mongo to the 8.0 LTS line too). - runs-on: ubuntu-24.04 + runs-on: ubuntu-latest # Real-service test gate. Every backend the suite can touch runs for real in # CI so the integration tests execute instead of skipping (the gap that let @@ -320,7 +315,7 @@ jobs: # green on the standalone. This leg keeps that from regressing. - name: Start MongoDB 8 replica set (27018) run: | - docker run -d --name tina4-mongo8-rs -p 27018:27018 mongo:8 \ + docker run -d --name tina4-mongo8-rs -p 27018:27018 mongo:8.0 \ mongod --replSet rs0 --bind_ip_all --port 27018 for i in $(seq 1 30); do docker exec tina4-mongo8-rs mongosh --port 27018 --quiet --eval 'db.runCommand({ping:1}).ok' >/dev/null 2>&1 && break