Hydra’s node upgrade exposed separate version pins across its tooling.

What happened.

Hydra moved cardano-node to 11.1.2. That change also brought cardano-cli to 11.2.3.0, which conflicted with a hardcoded 11.0.0.0 expectation in CardanoCliSpec. CardanoNodeSpec had its own version check alongside it.

A separate pin in demo/docker-compose.yaml remained on a 10.6.2 node container. That required its own bump to 11.1.2 after the network fault tolerance job broke. The upstream record also says the hydra-cluster build-and-test job broke during this work.

Why it matters.

The maintenance work shows that Hydra’s node version was represented in more than one place: its node dependency, a CLI-version assertion, and a demonstration container image. Updating one pin did not complete the upgrade, and the failures appeared in different CI jobs.

For teams vendoring Hydra or maintaining similar tooling, the signal is operational rather than protocol-level: an upgrade may require an audit of every separately maintained version expectation. The supplied record characterizes this as Layer 2 dependency and CI maintenance, not a Hydra release or a mainnet-affecting change.

What to watch next.

The next useful receipt is repository and CI evidence that the updated node, CLI expectation, and Docker Compose image are aligned, including the affected build-and-test and network fault tolerance jobs. Commit #2877 is the recorded consolidation point, but the supplied evidence does not provide a later CI result.