Skip to main content

Upgrading to 1.34.0

Released 2026-11-16. Everything in the release: changelog. How to upgrade: Upgrade.

What's new​

  • The dashboard says when a newer DeaconGuard is out: admins see the newest release beside the version in the sidebar, linked to its upgrade notes, and under Settings → New versions. See Knowing when there's a new release.

  • The install script works with sudo on RHEL, AlmaLinux, Rocky Linux, Oracle Linux, Amazon Linux and Fedora on machines without cosign, where it stopped with "the signature of checksums.txt is NOT valid" although the signature was never checked. The fixed script is at get.deaconguard.io for every release.

Before you upgrade​

Nothing to do. The database stays at schema 35, so a 1.33 server can still open it.

The server makes one new outbound request. About a minute after it starts, and then once a day, it reads the newest release's number from https://get.deaconguard.io/stable.txt. The request says nothing about your server: no version, no identifier, no numbers. If you don't want it:

  • Turn off Settings → New versions → Check for new versions after upgrading, or
  • set DEACONGUARD_UPDATE_CHECK=off in the server's environment before upgrading, so it never asks.

A server without internet access needs nothing: the request fails quietly and the dashboard shows no hint.

After you upgrade​

Nothing to do. Agents on 1.33 work with a 1.34.0 server and need no upgrade; agents make no such request.

Kubernetes, install script, packages and Docker Compose​

Nothing else to do. To stop the check before the server ever asks: with Helm, --set server.updateCheck=false; with Kustomize or Docker Compose, add DEACONGUARD_UPDATE_CHECK=off to the server's environment, as for any other server variable.