• v4.5.3 5819eac7f0

    v4.5.3
    All checks were successful
    CI / Backend lint (ruff) (push) Successful in 36s
    CI / Bot/backend version sync (push) Successful in 27s
    CI / Summarisation accuracy eval harness (stub provider) (push) Successful in 1m6s
    Release / Create Forgejo release (push) Successful in 17s
    CI / Does this change touch the recording path? (push) Successful in 25s
    CI / Which journeys does this change need? (push) Successful in 24s
    CI / Feedback site tests (push) Successful in 1m30s
    CI / Bot tests and audit (push) Successful in 3m46s
    CI / Docker image build (push) Successful in 5m3s
    Release / Build and push versioned images (push) Successful in 5m43s
    CI / Frontend (shard 2/2) (push) Successful in 7m53s
    CI / Frontend (shard 1/2) (push) Successful in 9m22s
    CI / Synthetic session harness (no GPU, no LLM) (push) Successful in 8m50s
    CI / End-to-end journeys (phone) (phone) (push) Successful in 20m13s
    CI / End-to-end journeys (keyboard) (keyboard) (push) Successful in 22m5s
    CI / End-to-end journeys (desktop) (desktop) (push) Successful in 22m12s
    CI / Backend migration, tests, and audit (push) Successful in 46m49s
    Stable

    claude-bot released this 2026-10-14 21:59:22 +00:00 | 454 commits to main since this release

    A wiki fix: merging a session's page into an existing one merges again, and a
    draft says the page's GM-only text is kept. Tried on the dev server as
    4.5.3-rc1.

    Upgrading from 4.5.2

    • No database migration, and BOT_CONTRACT_VERSION is unchanged (2). Pull
      the new images and docker compose up -d.

    Changed

    • [webapp] A wiki draft says your GM-only text is kept (#1195). The draft shows the page as the table reads it and puts every GM-only block back where it was on approve, but never said so, so a GM-only note looked dropped. When the page has GM-only text, the draft now says: "Your GM-only text isn't shown here. It stays on the page when you approve."

    Fixed

    • [webapp] Merging a session's page into an existing wiki page merges again, or says it couldn't (#1195). The merge capped the AI's reply at 2,048 tokens, which a model that thinks before answering could spend entirely, and the empty answer fell back to pasting the new paragraph under the page while the draft read as merged. The reply is uncapped now, like every other wiki rewrite, and a merge draft whose AI call fails is marked failed with the page untouched, so it can be started over.
    Downloads