Upgrading to 1.35.0
Released 2026-11-18. Everything in the release: changelog. How to upgrade: Upgrade.
What's new
- The GitHub action shows what it found on the run's Summary page, in private repositories and on every GitHub plan. See Where the results show.
- A refused upload to GitHub code scanning is a warning, and no longer fails the job. See Code scanning.
--summary FILEondeaconguard image scananddeaconguard config scanwrites the same summary for other pipelines.
Before you upgrade
Nothing to do. The database stays at schema 35, so a 1.33 or 1.34 server can still open it. Servers and agents behave as in 1.34.0; this release changes the pipeline checks only.
After you upgrade
In GitHub Actions, pin the action to v1.35.0 (uses: Cloudopsshell/deaconguard@v1.35.0) to get the Summary page and the warning. A workflow pinned to an earlier release keeps working as before.
If a workflow has upload-sarif: "true" and its repository is private without GitHub Code Security, the upload was failing the job; from v1.35.0 the job passes or fails on the findings, and a warning says the report wasn't uploaded. Remove upload-sarif there to drop the warning.
Kubernetes, install script, packages and Docker Compose
Nothing else to do.