v2.4.0

Fixed

• RPM upgrades no longer leave the stack stopped. RPM runs the new package's %post before the old package's %preun, so upgrading any of these packages used to stop its services and deregister its Prometheus targets right after the new version started them — dnf upgrade left monitoring down. The pre-removal scripts now only act on a real uninstall. If you're on an earlier 2.x rpm, this upgrade is the last one affected (the fix ships in the new package, but the old package's unguarded script still runs once): after upgrading, run sudo systemctl restart prometheus alertmanager grafana on the base host, restart any upgraded exporter services, and re-run the exporter registration if a target went missing — or simply reinstall the exporter package. Upgrades from v2.4.0 onward are clean. Debian installs were never affected.

Changed

• Removing a package now cleans up fully: the firewall port its install opened is closed, and systemd is reloaded so no stale Quadlet-generated unit lingers.
• Debian note: plain apt remove keeps the Quadlet .container file (standard dpkg conffile semantics), so the service stays defined and would start again on reboot. Use apt purge to remove a package's services for good. dnf remove has no such split.
• monitoring-add-exporter accepts bracketed IPv6 targets, e.g. [2001:db8::1]:9100.
• monitoring-configure-email handles SMTP passwords containing single quotes.

Internal

• CI now runs the full build + smoke tests on every push and PR (not just tags), with a shellcheck lint job and an upgrade-path regression test.
• Packaging manifests simplified via convention-based staging; built packages verified identical.