• v4.1.2 bbf25d9c67

    v4.1.2
    All checks were successful
    Release / Create Forgejo release (push) Successful in 13s
    CI / Bot/backend version sync (push) Successful in 43s
    CI / Backend lint (ruff) (push) Successful in 51s
    CI / Summarisation accuracy eval harness (stub provider) (push) Successful in 1m17s
    CI / Frontend tests, audit, and build (push) Successful in 1m54s
    CI / Bot tests and audit (push) Successful in 2m12s
    CI / Docker image build (push) Successful in 4m51s
    Release / Build and push versioned images (push) Successful in 4m40s
    CI / Backend migration, tests, and audit (push) Successful in 7m13s
    Stable

    claude-bot released this 2026-09-05 01:25:00 +00:00 | 311 commits to main since this release

    The AI provider you chose in v4.1.1 is now honoured everywhere, including the
    session summary itself. Upgrade straight past v4.1.1 if you have not already.

    No migrations. Nothing to rehearse, nothing to back out.

    The bot contract is unchanged (still v1), and nothing under /api/bot/*
    changed at all, so backend and bot images can be upgraded independently in
    either order.

    Under the hood every generation path now carries the configured LLM as one
    object instead of five loose parameters (#484). That is invisible to operators
    and changes no behaviour; it is what made the fix below a one-place change.

    Fixed

    • [webapp] The AI provider you chose is now used for session summaries and
      for the Test button, not just for everything else
      (#488). The provider
      select added in v4.1.1 was honoured when generating structured content and
      answering /ask, but two paths went on detecting the provider from the
      endpoint URL and ignoring your choice: writing the session summary itself,
      and Admin → Bot Settings' "Test LLM" button. This only affects you if you set
      the provider to something the URL does not already give away — typically a
      gateway or reverse proxy on your own domain — in which case summaries were
      being sent to the wrong service with credentials in the wrong header, usually
      failing outright, and the Test button reported on a connection nothing else
      in the product would have made. Nothing changes if you left the provider on
      "Detect from the URL".
    Downloads