• v4.7.1 e88538adb1

    v4.7.1
    All checks were successful
    CI / Backend lint (ruff) (push) Successful in 36s
    CI / Summarisation accuracy eval harness (stub provider) (push) Successful in 2m32s
    CI / Feedback site tests (push) Successful in 55s
    CI / Bot tests and audit (push) Successful in 2m14s
    CI / Bot/backend version sync (push) Successful in 53s
    CI / Does this change touch the recording path? (push) Successful in 22s
    Release / Create Forgejo release (push) Successful in 19s
    CI / Which journeys does this change need? (push) Successful in 23s
    Release / Build and push versioned images (push) Successful in 3m28s
    CI / Frontend (shard 2/2) (push) Successful in 10m0s
    CI / Docker image build (push) Successful in 9m9s
    CI / Frontend (shard 1/2) (push) Successful in 23m25s
    CI / Synthetic session harness (no GPU, no LLM) (push) Successful in 9m4s
    CI / Backend migration, tests, and audit (push) Successful in 47m57s
    CI / End-to-end journeys (phone) (push) Successful in 12m31s
    CI / End-to-end journeys (keyboard) (push) Successful in 23m14s
    CI / End-to-end journeys (desktop) (push) Successful in 24m31s
    Stable

    claude-bot released this 2026-11-06 08:02:42 +00:00 | 78 commits to main since this release

    One security fix for the bot, found by scanning the published 4.7.0 images.
    No migration, and BOT_CONTRACT_VERSION is 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 as 4.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