KITPro Server 0.1.0-alpha.12: Recoverable application operations and safer upgrades
KITPro Server v0.1.0-alpha.12 was published on September 22, 2026 as a public alpha for the Debian and Arch Linux baseline. It strengthens the work that happens when an operation is interrupted: replacing application containers, reconciling recorded state, restoring managed data, and upgrading KITPro itself.
Release record
KITPro Server 0.1.0-alpha.12 · Public alpha prerelease
Original release: . Retrospective release coverage. This article was published on . Created .
KITPro Server v0.1.0-alpha.12 was published on September 22, 2026 as a public alpha for the Debian and Arch Linux baseline. It strengthens the work that happens when an operation is interrupted: replacing application containers, reconciling recorded state, restoring managed data, and upgrading KITPro itself. This retrospective explains the release as it shipped. It is not an instruction to install an older alpha instead of the current public release.
KITPro Server is a browser-based manager for trusted self-hosted applications on Linux. It is separate from KITPro Linux Server, the operating-system distribution. Alpha.12 focuses on administrators who need a clear result when a browser disconnects or a host restarts during maintenance.
Operations that survive an interrupted request
An application operation can outlive the HTTP request that started it. Alpha.12 records durable outcomes so an exact replay of the same operation returns its recorded result. Reusing an operation ID for conflicting work is rejected. Per-installation serialization and fencing prevent an old executor from committing privileged changes after another executor has taken over.
Replacement now stages and verifies a new runtime generation before making it active. Multi-component applications keep progress for each component and respect dependency order during start and stop. The previous generation remains available when recovery may need it. If cleanup fails after a successful cutover, KITPro records cleanup debt rather than turning the completed replacement into an ambiguous failure.
Reconciliation and restore with explicit boundaries
A temporary container-runtime outage differs from a missing runtime. Alpha.12 preserves that distinction and classifies missing, stopped, drifted, unavailable, migrated, removed, and cleanup-pending state. Repair remains an explicit action tied to trusted recorded state. A deliberately removed runtime can settle into a stable reconciled state without KITPro blindly recreating it.
Restore uses a durable journal to record filesystem identity, swap progress, generated secrets, prior runtime state, and outstanding cleanup. After a crash, startup recovery can complete a proven forward state or restore the previous tree. When mixed storage state prevents a safe conclusion, it stops. These controls do not promise rollback of an irreversible application-data migration.
Alpha.11 upgrades require the release wrapper
The alpha.11-to-alpha.12 transition is a specific breaking operational boundary. Existing alpha.11 users must download the wrapper and matching package together from the official release, verify their checksums, and follow the tagged instructions. Raw Debian apt or dpkg installation, or raw Arch pacman -U, is unsupported for that transition. Fresh alpha.12 installations use the normal documented installation path.
The wrapper checks the incoming package and installed state and verifies the complete paired database backup before migration. The supported schema transition is 7 to 13. Downgrading after migration is unsupported. Alpha.12 also installs native package-upgrade protection for subsequent upgrades.
Platforms, verification, and limits
Debian and Arch Linux are the supported public baseline for this alpha; Rocky Linux and Podman remain Experimental. A running container is not proof of application readiness. Same-port replacement can cause a bounded interruption, and cleanup debt or failed restore trees may require an administrator's later decision.
Download packages, transition wrappers, the CycloneDX inventory, and kitpro-alpha12-SHA256SUMS from the official release. The Debian download filename uses 0.1.0.alpha12 while the installed Debian package version is 0.1.0~alpha12. Keep independent recoverable backups. This release provides neither arbitrary Compose management nor host-to-host restore. The tagged limitations and full release notes remain the authority for deployment decisions.
Resources
Official release and verified downloads
Product screenshots
