LoginSign Up
← Back to all sparks
Discourse logo

Discourse

SUPPORT
Velocity5.0

Open-source community discussion and support platform

www.discourse.org ↗

Monthly releases on time, security out-of-band, and the changelog living somewhere else

monthly-release-trainsecurity-patchesself-hostedlong-term-branchesadmin-documentation
◆Current state
Discourse ships a dated minor every month — 2026.4 through 2026.7 in this window — and back-patches several supported branches alongside each one. Critical security fixes travel separately as out-of-band intermediate releases, the most recent on July 31 covering the 2026.8 pre-release line plus the 2026.7, 2026.6 and 2026.1 branches. The release topics carry no detail of their own; each links out to releases.discourse.org. The remainder of the feed is administrator documentation.
◆Where it's heading
The cadence is the signal and it has not wavered: a monthly minor, patches reaching back to branches cut in January, and security decoupled from the feature train. That is the maintenance posture of self-hosted software whose installs upgrade on their own schedule, and the branch count is the tell — still patching 2026.1 at the end of July means an install that has sat still for six months is covered. Where the product is actually heading surfaces in the documentation instead, where the AI bot's support for external MCP servers is the only entry in the last ten describing a capability rather than a version number.
◆Prediction
The August 2026 monthly release is the near-certain next entry, in the same pointer-topic shape. What lands inside it cannot be read from this feed — these topics are links, so any call on direction would have to come from the linked changelog.

◆Recent moves

  1. 11d ago

    July 31st 2026 intermediate releases

    An out-of-band security release covering four lines at once — the 2026.8 pre-release plus the 2026.7, 2026.6 and 2026.1 branches. It demonstrates the support commitment the monthly train only implies: a branch cut in January still receives critical fixes in July. No feature content, by design.

    View source ↗
  2. 14d ago

    July 2026 monthly release

    The 2026.7 minor, on schedule, with patch releases for the 2026.1, 2026.5 and 2026.6 branches alongside it. The topic links to the changelog rather than listing changes, so the release's substance is not visible from the feed — only its punctuality.

    View source ↗
  3. 1mo ago

    June 2026 monthly release

    2026.6, on the same monthly beat, with back-patches to 2026.1, 2026.4 and 2026.5. The three-branch patch spread is the routine here rather than the exception.

    View source ↗
  4. 2mo ago

    May 2026 monthly release

    2026.5 arrives on time but with no accompanying patch releases listed — the one month in this window where the back-branch work is absent from the topic.

    View source ↗
  5. 2mo ago

    May 19th 2026 intermediate releases

    The previous out-of-band security drop, spanning the 2026.5 pre-release line and the 2026.4, 2026.3 and 2026.1 branches. Paired with the July 31 release it sets the rhythm: critical fixes arrive on their own schedule and are never folded into the monthly train.

    View source ↗
  6. 3mo ago

    April 2026 monthly release

    2026.4, the earliest release in the window, in identical pointer-topic form. The consistency of the format across four months is itself the finding: this feed reports that a release happened, not what it contained.

    View source ↗