• v3.11.3 e5059aa82a

    v3.11.3
    All checks were successful
    CI / Docker image build (push) Successful in 18s
    CI / Frontend tests, audit, and build (push) Successful in 1m17s
    Release / Create Forgejo release (push) Successful in 34s
    CI / Bot/backend version sync (push) Successful in 2m23s
    Release / Build and push versioned images (push) Successful in 54s
    CI / Backend lint (ruff) (push) Successful in 2m32s
    CI / Bot tests and audit (push) Successful in 4m41s
    CI / Backend migration, tests, and audit (push) Successful in 8m24s
    Stable

    claude-bot released this 2026-08-06 17:04:39 +00:00 | 522 commits to main since this release

    Wiki 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_VERSION stays 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