rust-proxmox-upgrade-checks (1.1.1-1) trixie; urgency=medium * detect an upgrade to a 1.0 release as done for products that were still at 0.x before, like the Datacenter Manager, whose upgraded package got reported as too old, which in turn made all follow-up checks run in their not yet upgraded variant. -- Proxmox Support Team Tue, 04 Aug 2026 00:02:58 +0200 rust-proxmox-upgrade-checks (1.1.0-1) trixie; urgency=medium * kernel check: compare the parsed version instead of matching patterns: - accept the 7.0 kernel of the trixie based releases, which got reported as unexpected before, and any future series without needing an update here. - report a kernel that was backported to the release upgraded from, marked as 'bpo12' for bookworm, as one still to be rebooted from. Those passed as an already upgraded kernel until now. - point at any installed kernel meta-package that would be suitable to boot, which covers the opt-in ones like 6.17 too. * dkms check: pass the running kernel release on without the trailing newline, as dkms could not match any module for such a version and thus always reported that none are installed. * allow products to configure the kernels expected before and after the upgrade, as those differ per major upgrade. -- Proxmox Support Team Sun, 02 Aug 2026 21:59:29 +0200 rust-proxmox-upgrade-checks (1.0.2-1) trixie; urgency=medium * re-build for proxmox-apt 1.0 and proxmox-apt-api-types 3.0; the enum-fallback Cargo feature on both crates is gone and no longer requested. -- Proxmox Support Team Tue, 19 May 2026 13:30:00 +0200 rust-proxmox-upgrade-checks (1.0.1-1) trixie; urgency=medium * adapt check for the version of the old-package on upgrade now being an Option, like it can happen when a new dependency is pulled in, as then there cannot be an old option. -- Proxmox Support Team Sun, 30 Nov 2025 21:01:20 +0100 rust-proxmox-upgrade-checks (1.0.0-1) trixie; urgency=medium * Initial release. -- Proxmox Support Team Tue, 16 Sep 2025 16:47:42 +0100