Skip to content

Upgrading to Canvus 26.07

This release breaks client compatibility

Canvus Server 26.07.x does not accept connections from clients older than 26.07. Upgrading the server is no longer an independent step — every client that uses it must move to 26.07 as part of the same change window.

What changed

Up to and including the 26.6 series, Canvus Server accepted connections from older clients. From 26.07.0 onwards it does not.

Compatibility is now one-directional:

Client Server Result
26.07.x 26.07.x Supported
26.07.x 3.x or 26.4–26.6 Supported — the client works against the older server
3.x or 26.4–26.6 26.07.x Not supported — the client cannot safely connect

The practical consequence: clients can run ahead of the server, but never behind it. A 26.07 client talking to a 3.x server is fine. A 3.x client talking to a 26.07 server is not.

This inverts the guidance in Upgrading to Canvus 26.4, where either order worked and rollout could be incremental.

Before you upgrade

Inventory every client that connects to the server you are about to upgrade — video wall machines, desktops, laptops, and any unattended or kiosk installs that are easy to forget. Each one needs a 26.07 client before the server moves.

If you cannot upgrade every client in the same window, do not upgrade the server yet. There is no compatibility mode and no server-side setting that re-enables older clients.

Upgrade procedure

Because clients tolerate a newer-client/older-server pairing but not the reverse, upgrade clients first:

  1. Verify your maintenance entitlement and license cover the 26.07 release. Contact sales if you are unsure.
  2. Upgrade every client to 26.07.x. They keep working against your existing server while you work through the estate.
  3. Confirm no client older than 26.07 remains in service.
  4. Upgrade the server. For containerised deployments see the Canvus Server installation guide; for standalone installs see the Downloads page.
  5. Verify connectivity from a sample of upgraded clients.

This is the reverse of the 26.4 recommendation

26.4 recommended server-first. For 26.07, client-first is the only order that avoids an outage.

Container channel note

:stable now points at 26.07.9. The downloaded podman-compose.yml pins :stable, so a container deployment that was safe to run unchanged before this release will now pull a 26.07 server and stop accepting your older clients.

This applies to a podman-compose pull on an existing deployment as much as to a fresh install — pulling :stable moves you onto 26.07 without any tag change on your side. Upgrade your clients before you next pull.

To hold on a pre-26.07 server while you work through the client estate, pin an explicit version tag instead of tracking :stable. See Container image tags and channels.

What is not changing

  • Your data. No migration is required for the client compatibility change.
  • Your configuration files. No config changes are needed for the upgrade.