LoginSign Up
← Back to all sparks
ClickHouse logo

ClickHouse

INFRA · APISANALYTICS
Velocity5.0

Fast open-source column-oriented database for analytics

clickhouse.com ↗

ClickHouse is shipping six active version branches in parallel — but the captured feed has only tags, no notes.

parallel maintenance brancheslts cadenceversion-only entriesscraping issueopen source database
◆Current state
What's visible in the captured feed is high-cadence GitHub release tagging across at least six parallel branches in two weeks: 25.8.x-lts, 25.10.x, 25.12.x, 26.1.x, 26.2.x, and 26.5.x. Each entry is title-only with no release notes captured. The branch fan-out is itself meaningful — ClickHouse is maintaining LTS plus several stable branches simultaneously, which is the cadence pattern of a mature OSS database serving enterprises that pin to specific minor versions.
◆Where it's heading
Without per-release content we can't comment on feature direction. The branch shape says enterprise-grade backporting is alive and well; the new 26.5 branch starting in late April implies a forward-development cycle is underway alongside the maintenance work. Worth fixing the changelog ingest to pull release-note bodies from GitHub before the next pass — there's a real signal here being lost.
◆Prediction
Once the scraper captures release-note bodies, expect to see continued cherry-pick patches on 25.x-LTS for at least 12 more months in parallel with 26.x feature work. Unable to predict feature direction from version tags alone.

◆Recent moves

  1. 1mo ago

    Patch on 25.8 LTS branch (notes not captured)

    LTS branch patch — release notes weren't captured by the scraper, so the specific change set is unknown. Fits the pattern of ongoing backports to the 25.8 LTS for enterprises pinned to that line.

    View source ↗
  2. 1mo ago

    Patch on 26.2 stable branch (notes not captured)

    Stable-branch patch on the 26.2 line. No body content captured; classified as a maintenance/improvement release based on the patch-level version.

    View source ↗
  3. 1mo ago

    Patch on 25.12 stable branch (notes not captured)

    Stable-branch release on 25.12. No notes captured; the patch-level version implies maintenance scope rather than new features.

    View source ↗
  4. 1mo ago

    Patch on 25.10 stable branch (notes not captured)

    Patch release on the 25.10 stable branch. No notes captured; classified as maintenance work based on version pattern.

    View source ↗
  5. 1mo ago

    Patch on 25.12 stable branch (notes not captured)

    Earlier patch on 25.12 stable branch (preceded the 25.12.12 release that came four days later). Maintenance scope based on version pattern; no body captured.

    View source ↗
  6. 2mo ago

    Patch on 25.12 stable branch (notes not captured)

    Earlier patch on 25.12 stable branch. Same data caveat — the scraper captured only the version tag, not the GitHub release body.

    View source ↗