Skip to content

ci: roll pinned ClickHouse versions forward to LTS + 3 latest - #960

Open
polyglotAI-bot wants to merge 2 commits into
mainfrom
polyglot/ci-ch-version-window
Open

ci: roll pinned ClickHouse versions forward to LTS + 3 latest#960
polyglotAI-bot wants to merge 2 commits into
mainfrom
polyglot/ci-ch-version-window

Conversation

@polyglotAI-bot

Copy link
Copy Markdown
Collaborator

Summary

Roll the stale pinned ClickHouse version window in CI forward to the current support set.

The integration-tests-local-single-node job in .github/workflows/tests-node.yml pinned node: 24 against a now-stale window of ClickHouse server versions — 26.2, 26.1, 25.12, 25.11, 25.10 — all outside the current support window. This replaces them with the current support set:

  • 25.8 (LTS)
  • 26.3 (LTS)
  • 26.5, 26.6, 26.7 (3 latest)

The base matrix (clickhouse: [head, latest]) is unchanged and continues to cover the bleeding edge; only the explicit include: pins are rolled forward. js's window model (a spread of pinned minors alongside head/latest) is preserved.

Why

ClickHouse 26.7 has been released and 26.4 reached EOL, so the pinned window (newest pin was 26.2) had drifted behind the supported releases. Pinning both current LTS lines (25.8, 26.3) plus the three newest minors keeps the version-specific regression coverage meaningful. Maintainer request, 2026-07-23.

Notes

  • CI-only change — no client code, no public API or observable-behavior change, so no CHANGELOG entry (per AGENTS.md, changelogs are for observable-behavior / public-API changes) and no version bump.
  • All five image tags verified present on Docker Hub (docker manifest inspect clickhouse/clickhouse-server:<v>).

Test plan

  • The node workflow's integration-tests-local-single-node matrix runs green on 25.8, 26.3, 26.5, 26.6, 26.7 (node 24).

The integration-tests-local-single-node job pinned a stale window of ClickHouse versions (26.2, 26.1, 25.12, 25.11, 25.10), all now outside the current support window. Replace them on node 24 with the current support set: 25.8 (LTS), 26.3 (LTS), 26.5, 26.6, 26.7 (3 latest). The [head, latest] base matrix continues to cover the bleeding edge. CI-only change; no client behavior change.
Copilot AI review requested due to automatic review settings July 23, 2026 19:43
@codecov

codecov Bot commented Jul 23, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Node CI workflow’s pinned ClickHouse server versions for the integration-tests-local-single-node job to match the currently supported window (current LTS lines plus the 3 latest minors), while keeping the existing head/latest baseline coverage intact.

Changes:

  • Replaces the stale pinned ClickHouse minors in the matrix include: list with 25.8, 26.3, 26.5, 26.6, 26.7 (Node 24, default log level).
  • Leaves the base matrix (clickhouse: [head, latest]) unchanged to continue covering bleeding-edge versions.

Comment thread .github/workflows/tests-node.yml Outdated
Unquoted YAML scalars parse as floats (e.g. 26.10 -> 26.1), which would
interpolate into the wrong Docker image tag (clickhouse/clickhouse-server)
on a future window roll. Quoting the pinned versions keeps them as strings
matching the server tags. The current set already round-trips safely; this
hardens the matrix against later rolls.

Addresses Copilot review feedback on #960.
Copilot AI review requested due to automatic review settings July 23, 2026 20:03

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants