Skip to content

DevGuard Release v1.18.0

Choose a tag to compare

View all tags
@timbastin timbastin released this 06 Nov 16:18
· 53 commits to main since this release
v1.18.0
This tag was signed with the committer’s verified signature.
timbastin Tim Bastin
SSH Key Fingerprint: ps8GXP45By+yuQ918pMDSUyBBfE8mH/7SadnTk0F+xc
Verified
Learn about vigilant mode.
f3954e6
This commit was signed with the committer’s verified signature.
timbastin Tim Bastin
SSH Key Fingerprint: ps8GXP45By+yuQ918pMDSUyBBfE8mH/7SadnTk0F+xc
Verified
Learn about vigilant mode.

🚀 DevGuard Release v1.18.0

Note

Released manually: the cross-registry digest check failed for a harmless reason

Every DevGuard image is built twice, separately: on GitHub Actions (ghcr.io) and on GitLab CI (registry.opencode.de). The two digests must match before a release goes out. For this release, devguard and kratos matched, but postgresql and scanner did not. That blocked the automated release.

We compared the differing layers file by file. No executable code differs. The only differences are:

  • postgresql: aiohttp (a dependency of barman) writes small .hash metadata files that contain the absolute build directory. That directory differs between the two CI systems (/build/... vs /nix/var/nix/builds/...). All compiled .so files are byte-identical.
  • scanner (arm64 only): one compiled Python bytecode file for a test module of networkx differs, only in CPython's marshal reference flags (a known CPython non-determinism). The bytecode instructions are the same.

Because of this, no binaries are attached to this release. v1.18.2 fixes the postgresql cause (barman no longer gets local Python overrides, so its dependencies come from the binary cache instead of being rebuilt on each CI) and restores the automated release. Use v1.18.2 for binaries.

Secure software supply chain scanning and security analysis platform

🔍 DevGuard Scanner

The Scanner performs software supply chain analysis, SBOM generation, vulnerability detection, and security scanning. It communicates with a running devguard-api instance.

🐳 Container Image

docker pull ghcr.io/l3montree-dev/devguard/scanner:v1.18.0

Go Install

go install github.com/l3montree-dev/devguard/cmd/devguard-scanner@v1.18.0

🛡️ DevGuard Platform

The DevGuard Platform provides centralized security visibility, findings management, and reporting.

🐳 Container Image

docker pull ghcr.io/l3montree-dev/devguard:v1.18.0

The frontend image (devguard-web) is released separately — see devguard-web releases for the matching v1.18.* release.

☸️ Kubernetes Deployment

Deploy DevGuard to Kubernetes using the official Helm chart.

Helm Chart

oci://ghcr.io/l3montree-dev/devguard-helm-chart/devguard

Install

helm install my-devguard \
  oci://ghcr.io/l3montree-dev/devguard-helm-chart/devguard \
  --version 1.18.0

Versioning

All DevGuard components (devguard, devguard-web, Helm chart) share the same minor version. Any v1.18.* release of one component is compatible with any v1.18.* release of another. Patch versions are released independently per component — you do not need to upgrade all components simultaneously as long as the minor version matches.

📖 See VERSIONING.md for the full policy.
📋 See CHANGELOG for what changed in this release.

Resources

📖 Documentation: https://github.com/l3montree-dev/devguard

🐛 Report Issues: https://github.com/l3montree-dev/devguard/issues

💬 Community Discussions: https://github.com/l3montree-dev/devguard/discussions

Assets 2
Loading