---
title: Supported versions
---

Releases N and N−1 get fixes, and an SDK at `X.Y` works with a server at `X.Y` or `X.(Y−1)`. Loom
ships one version for the server, both images, the web app, both SDKs, the root skills and the Helm
chart's `appVersion` ([release process](/development/release-process)). This page also covers
the coding-agent plugins and how a change that removes something is announced.

## Release lines

| Line | What it gets                                                                                      |
| ---- | ------------------------------------------------------------------------------------------------- |
| N    | the newest minor release (`X.Y`): every fix, as a patch release (`X.Y.(Z+1)`) when it cannot wait |
| N−1  | the minor release before it: security fixes and fixes for data loss or a wrong answer, as patches |
| N−2  | none: upgrade to N or N−1                                                                         |

A minor release comes from `main` about every two weeks; a patch comes from the line's
`release/X.Y` branch, with the fix merged to `main` first. An upgrade follows
[upgrades](/operations/upgrades); two adjacent versions serve side by side while one replaces the other
([rolling upgrades](/architecture/rolling-upgrades)).

## SDKs and servers

The SDKs (`clickhouse-loom` on PyPI, `@clickhouse/loom` on npm) are published with every release, at
the server's version; npm's `latest` names the highest final, and a patch to an older line takes its
`release-X.Y` dist-tag. Against the older server:

- a field the SDK sends that the older server does not know is served and named in the answer's
  `ignored_args`, except on an op that changes state, where a key the server reads as a misspelling
  of one of its fields (a near name, a synonym, a word of a field's name) is refused with
  `422 UNKNOWN_ARGUMENT` and nothing is written
  ([unknown and removed fields](/reference/http-api#unknown-and-removed-fields));
- an operation the older server does not serve answers `404`, which the SDKs raise as `NotFound`
  (Python `loom.errors.NotFound`, TypeScript `NotFound`): a call never succeeds silently against a
  server that cannot do it. The same error means a missing row, so a client that must tell the two
  apart reads `ops.capabilities` at start-up
  ([discovering what a deployment serves](/reference/http-api#discovering-what-a-deployment-serves)).

A major release (`X.0`) may break the rule against the last `(X−1).Y` server; its release notes
say what an SDK at `X.0` needs.

An older SDK keeps working against a newer server for as long as the server serves what it calls;
a removal follows the rule below.

## Coding-agent plugins

The Claude Code and Codex plugins carry their own version, and name the oldest server their
hooks support (`MIN_SERVER_VERSION` in `lib/server-version.mjs`). A session against an older
server starts with one `loom:` line saying so, and the plugin goes on working where it can
([Claude Code](/features/integrations/claude-code)). The Claude Code plugin needs Claude Code
2.1.139 or newer, the first that runs a hook's `args` with no shell.

## Removing something

A removal is announced, by hand in the release pull request, in the release notes of the minor
release before the one that removes it, under "What changed for clients". Until the removal, the
server serves the old field or op; after it, a removed request field is still accepted and named
in `ignored_args`, so a client sending it learns of the change without failing, and a removed op
answers `404` (`NotFound`), which `ops.capabilities` tells apart from a missing row.

## Release artifacts

Every release image is built on the architecture it runs on, scanned for critical vulnerabilities
with a fix, and published with its provenance and an SBOM. Each image's multi-arch index carries a
keyless signature from the release workflow; [container images](/operations/deployment#container-images)
gives the `cosign verify` command. Each file on the GitHub Release is signed the same way, in a
`<file>.sigstore.json` beside it; [release files](/operations/deployment#release-files) gives the
`cosign verify-blob` command.
