-
v4.7.1
StableAll checks were successfulCI / Backend lint (ruff) (push) Successful in 36sCI / Summarisation accuracy eval harness (stub provider) (push) Successful in 2m32sCI / Feedback site tests (push) Successful in 55sCI / Bot tests and audit (push) Successful in 2m14sCI / Bot/backend version sync (push) Successful in 53sCI / Does this change touch the recording path? (push) Successful in 22sRelease / Create Forgejo release (push) Successful in 19sCI / Which journeys does this change need? (push) Successful in 23sRelease / Build and push versioned images (push) Successful in 3m28sCI / Frontend (shard 2/2) (push) Successful in 10m0sCI / Docker image build (push) Successful in 9m9sCI / Frontend (shard 1/2) (push) Successful in 23m25sCI / Synthetic session harness (no GPU, no LLM) (push) Successful in 9m4sCI / Backend migration, tests, and audit (push) Successful in 47m57sCI / End-to-end journeys (phone) (push) Successful in 12m31sCI / End-to-end journeys (keyboard) (push) Successful in 23m14sCI / End-to-end journeys (desktop) (push) Successful in 24m31sreleased this
2026-11-06 08:02:42 +00:00 | 78 commits to main since this releaseOne security fix for the bot, found by scanning the published 4.7.0 images.
No migration, andBOT_CONTRACT_VERSIONis unchanged (2). To upgrade from
4.7.0:make backup-now,git checkout v4.7.1 && docker compose pull && docker compose up -d. Tried on the dev server as4.7.1-rc1.Security
- [bot] The bot's certificate bundle is updated (certifi 2025.11.12 → 2026.10.23, GHSA-6q48-6c7w-9gw2): the old bundle trusted emSign root CAs whose intermediate keys were compromised. The backend and frontend images were already clean (#1343).
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads