-
v4.5.3
StableAll checks were successfulCI / Backend lint (ruff) (push) Successful in 36sCI / Bot/backend version sync (push) Successful in 27sCI / Summarisation accuracy eval harness (stub provider) (push) Successful in 1m6sRelease / Create Forgejo release (push) Successful in 17sCI / Does this change touch the recording path? (push) Successful in 25sCI / Which journeys does this change need? (push) Successful in 24sCI / Feedback site tests (push) Successful in 1m30sCI / Bot tests and audit (push) Successful in 3m46sCI / Docker image build (push) Successful in 5m3sRelease / Build and push versioned images (push) Successful in 5m43sCI / Frontend (shard 2/2) (push) Successful in 7m53sCI / Frontend (shard 1/2) (push) Successful in 9m22sCI / Synthetic session harness (no GPU, no LLM) (push) Successful in 8m50sCI / End-to-end journeys (phone) (phone) (push) Successful in 20m13sCI / End-to-end journeys (keyboard) (keyboard) (push) Successful in 22m5sCI / End-to-end journeys (desktop) (desktop) (push) Successful in 22m12sCI / Backend migration, tests, and audit (push) Successful in 46m49sreleased this
2026-10-14 21:59:22 +00:00 | 454 commits to main since this releaseA 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_VERSIONis unchanged (2). Pull
the new images anddocker 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
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
- No database migration, and