Replaces 2.0.1, whose notes are folded in below: on a node updated with install.sh, 2.0.1 could leave a CrowdSec repository entry that stopped every later update.
A wrong CrowdSec suite can no longer stop an update
On a node installed or updated with install.sh, the CrowdSec repository entry could end up naming the node's own Debian suite — trixie, which CrowdSec does not publish — and from then on every apt-get update, and so every update of the app, failed on that source before anything was touched.
The repository is now used through one fixed line (the bookworm build, a static binary that runs on anything newer); the installer rewrites a wrong entry before it updates; and a source apt cannot read is a warning, not the end of the update. Nothing to do: the next update from Settings › Updates heals the entry itself.
A node installed from a package updates from the Updates page too
The one-click update only knew the installer's node — its unit under /etc/systemd/system — and told a node installed from the .deb or .rpm, the Proxmox container among them, that it was "not installer-managed". Running install.sh there would have been wrong anyway: dpkg's files overwritten, its database left behind.
Such a node now fetches the release's package and installs it with apt or dnf, so the package manager stays in step and the service restarts as usual. A package node takes releases (and pre-releases when betas are offered), never a branch: a version pushed ahead of its release says so in the update log instead of half-installing.
Also: the Proxmox container script now tells the community-scripts helpers that a pre-release is wanted when the node has Also offer beta versions ticked — they refused a pinned beta with "No stable releases found" (#19).
Image: ghcr.io/avandeputte/haproxy-manager:2.0.2