agentleFS
ClickHouseClickHouse/clickhouse-connect/.claude/skills/update-test-matrix/SKILL.md

update-test-matrix

Skill536 starsChanged 4 days agoApache-2.0View on GitHub

Refresh the shared ClickHouse server release series in .github/clickhouse-versions.json from currently supported releases. Use when the user wants to update CI coverage for new ClickHouse releases.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    All single-version jobs and the main matrix's extra include entries consume this default automatically.

    line 35
  2. Very specific:

    If the default changes, also update the two CLICKHOUSE_CONNECT_TEST_CH_VERSION fallbacks in docker-compose.yml and the standalone ARG …

    line 38

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Update Test Matrix

.github/clickhouse-versions.json owns the server matrix and its default. The reusable .github/workflows/clickhouse-versions.yml exposes both to the main, Rust binding, and core publishing workflows. Keep release-series tags such as 26.3: patch updates are intentional. New series enter CI through a reviewed manifest change.

Select supported versions

Fetch https://raw.githubusercontent.com/ClickHouse/ClickHouse/master/SECURITY.md. Collect the supported rows as major.minor strings.

Classify those series using ClickHouse release tags:

gh api 'repos/ClickHouse/ClickHouse/releases?per_page=100' --paginate --jq '.[].tag_name'

Tags ending in -lts identify LTS series; others end in -stable. The x.3 and x.8 LTS convention is a sanity check. Paginate further if a supported series has no release in the first page.

Take the union of the three latest supported series and the two latest supported LTS series. An LTS series can be in both groups. Deduplicate and sort numerically in ascending order.

Update the manifest and local fallbacks

Set matrix to the selected series and default to the oldest selected LTS. All single-version jobs and the main matrix's extra include entries consume this default automatically. Keep their expressions and the dependency profiles intact.

If the default changes, also update the two CLICKHOUSE_CONNECT_TEST_CH_VERSION fallbacks in docker-compose.yml and the standalone ARG CLICKHOUSE_VERSION default in .docker/clickhouse/single_node_tls/Dockerfile. Compose and Docker cannot read the JSON directly, so check these fallbacks when changing the default. TLS must continue to use the same selected version as the ordinary server.

The scheduled clickhouse_ci.yml intentionally tests Cloud and head. Leave it as is when refreshing the supported matrix.

Validate and summarize

Validate the affected workflows with actionlint when available. Check that the manifest has unique release-series entries and its default belongs to the matrix. Check docker compose config with the override unset and with each selected series: the ordinary image and TLS build argument must select the same version.

Report the supported series and their classification, the old and new matrix, the default, and any local fallback updates. Do not commit unless the user has authorized a commit.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.