Docker image tags 2.1.5-2.1.7 all ship Rivet 2.1.4 binary

[Crunchyman-ralph]

Description

All Docker image tags from 2.1.5 through 2.1.7 contain the same Rivet 2.1.4 binary (built 2026-03-03). The tags are being created but the binary isn't being rebuilt.

After recently releasing 2.1.7, docker images need to be built with this new version or else upgrading to 2.1.7 breaks the environment

Steps to reproduce

docker run --rm rivetdev/engine:2.1.7 --version
# Output: Rivet 2.1.4
# Build Timestamp: 2026-03-03T00:08:13.658230172Z

docker run --rm rivetdev/engine:2.1.6 --version
# Output: Rivet 2.1.4 (same)

Impact

rivetkit SDK 2.1.7 has protocol changes (e.g. the run handler exit behavior fix in #startRunHandler) that require a matching engine binary. Using rivetkit 2.1.7 with the 2.1.7 Docker image results in:

level=WARN msg="runner disconnected" code=1011 reason=ws.invalid_packet
Actor failed to start: "no_capacity"

This forces users to pin rivetkit to 2.1.6 to match the actual 2.1.4 engine binary.

Expected behavior

rivetdev/engine:2.1.7 should contain the Rivet 2.1.7 binary built from the v2.1.7 tag.

Environment

• Docker image: rivetdev/engine:2.1.7 (sha256:27ac27ce7687)
• rivetkit SDK: 2.1.7
• Platform: linux/amd64

[linear]

RVT-6121

[NathanFlurry]

Thx! Will fix in next release.