Artemis Studio

2026.09.73 — 2026-09-30

Support Artemis 2.33.0 to 2.57.0 and refuse older brokers (11906957)
Studio now states the Artemis releases it supports: 2.33.0 to 2.57.0. The new "Supported broker versions" guide page lists the range, the images CI tests and how the minimum was chosen. ActiveMQ Classic is not supported.
- Registering a cluster reads each seed's broker version. A broker older than 2.33.0 is refused with a 422 naming the minimum, on the connection check and the registration alike, and nothing is stored. A broker newer than 2.57.0 is registered with a warning that it is untested.
- Every node reports where its version sits against the range (versionSupport), and the topology says in words when a node runs an unsupported or untested release. A node found later below the minimum stays in the cluster, flagged.
- Creating a divert, including through message capture, plugin taps and a configuration apply, works on brokers before 2.38 by falling back to the positional createDivert, transformer included.
- An operation that needs a newer release than a node runs can be declared as a version gate: the capabilities list it with the release it needs (versionGates), and a command skips older nodes, reporting them UNSUPPORTED_VERSION rather than failed. No operation needs one today.
- CI runs the backend suite against both ends of the range, and the dev and demo stacks run apache/artemis:2.57.0.

Support Artemis 2.33.0 to 2.57.0 and refuse older brokers (11906957)
Studio now states the Artemis releases it supports: 2.33.0 to 2.57.0. The new "Supported broker versions" guide page lists the range, the images CI tests and how the minimum was chosen. ActiveMQ Classic is not supported.
- Registering a cluster reads each seed's broker version. A broker older than 2.33.0 is refused with a 422 naming the minimum, on the connection check and the registration alike, and nothing is stored. A broker newer than 2.57.0 is registered with a warning that it is untested.
- Every node reports where its version sits against the range (versionSupport), and the topology says in words when a node runs an unsupported or untested release. A node found later below the minimum stays in the cluster, flagged.
- Creating a divert, including through message capture, plugin taps and a configuration apply, works on brokers before 2.38 by falling back to the positional createDivert, transformer included.
- An operation that needs a newer release than a node runs can be declared as a version gate: the capabilities list it with the release it needs (versionGates), and a command skips older nodes, reporting them UNSUPPORTED_VERSION rather than failed. No operation needs one today.
- CI runs the backend suite against both ends of the range, and the dev and demo stacks run apache/artemis:2.57.0.

Stop the registration form claiming the details changed after a failed check (23e992f3)
A connection check that failed told the operator to check again because the details had changed, when nothing had been edited. It now says the check failed and to fix what it reports; the changed-details hint stays for a check made stale by an edit.