-
v3.11.3
StableAll checks were successfulCI / Docker image build (push) Successful in 18sCI / Frontend tests, audit, and build (push) Successful in 1m17sRelease / Create Forgejo release (push) Successful in 34sCI / Bot/backend version sync (push) Successful in 2m23sRelease / Build and push versioned images (push) Successful in 54sCI / Backend lint (ruff) (push) Successful in 2m32sCI / Bot tests and audit (push) Successful in 4m41sCI / Backend migration, tests, and audit (push) Successful in 8m24sreleased this
2026-08-06 17:04:39 +00:00 | 522 commits to main since this releaseWiki entry summaries came out as JSON.
v3.11.2 was tagged but never deployed to production — this bug was caught on
the dev deploy and supersedes it. Upgrade straight to 3.11.3. No migrations;
BOT_CONTRACT_VERSIONstays 1.Fixed
-
[webapp] Wiki entry summaries were generated as JSON instead of prose. The
summary generator asked the model for "plain prose only" while the underlying
transport was still in JSON mode with the lore-proposal instructions attached,
so entries came out with a summary of{"proposals":[]}. The bug predates
v3.11.2, but was only reachable through the manual "regenerate summary" button;
v3.11.2 made summaries generate automatically on every approval, which would
have written JSON into the summary of every entry a GM approved. (#285)Existing installs are unlikely to be affected — the generator had no automatic
trigger before v3.11.2, so only entries where the manual button was used could
carry a JSON summary. Re-running "regenerate summary" on such an entry now
produces prose.
Downloads
-
Source code (ZIP)
0 downloads
-
Source code (TAR.GZ)
0 downloads
-