Skip to content

KITPro Server v0.1.0-alpha.12

Pre-release
Pre-release

Choose a tag to compare

@keepittechie keepittechie released this 22 Sep 04:40
· 84 commits to main since this release

KITPro Server v0.1.0-alpha.12

KITPro Server v0.1.0-alpha.12 is an alpha prerelease for Debian and Arch Linux. It improves lifecycle recovery, reconciliation, backup and restore, and package-upgrade safety.

Important upgrade instructions for alpha.11 users

Alpha.11 users must use the transition wrapper for their package format. Do not run a raw package-manager upgrade from alpha.11.

Debian alpha.11 to alpha.12

Download kitpro-debian-upgrade and kitpro-server_0.1.0.alpha12_amd64.deb from this release, keep them in the same working directory, then run:

chmod +x kitpro-debian-upgrade
sudo ./kitpro-debian-upgrade ./kitpro-server_0.1.0.alpha12_amd64.deb

The wrapper validates the installed alpha.11 state, creates and verifies the complete database backup set, verifies the exact alpha.12 package by SHA-256 and package metadata, and invokes the upgrade only after preflight succeeds.

GitHub exposes the package with 0.1.0.alpha12 in the filename. The installed Debian package version remains 0.1.0~alpha12.

Direct apt install ./kitpro-server_0.1.0.alpha12_amd64.deb or dpkg -i is unsupported specifically for the alpha.11 to alpha.12 transition.

Arch Linux alpha.11 to alpha.12

Download kitpro-server-0.1.0_alpha12-1-upgrade.sh and kitpro-server-0.1.0_alpha12-1-x86_64.pkg.tar.zst from this release, keep them in the same working directory, then run:

chmod +x kitpro-server-0.1.0_alpha12-1-upgrade.sh
sudo ./kitpro-server-0.1.0_alpha12-1-upgrade.sh ./kitpro-server-0.1.0_alpha12-1-x86_64.pkg.tar.zst

The wrapper verifies the exact package, establishes a temporary fail-closed pre-transaction gate, and performs the supported transition.

Raw pacman -U is unsupported specifically for the alpha.11 to alpha.12 transition.

Alpha.12 installs permanent native package-upgrade protection for future upgrades.

Fresh installation

New alpha.12 installations can use the normal documented Debian or Arch installation path. The transition wrappers above are only for existing alpha.11 installations.

Reliability

  • Lifecycle operations are durable across interruption and API response loss.
  • Exact operation replay returns the recorded result, while conflicting reuse of an operation ID is rejected.
  • Per-installation serialization and fencing prevent stale executors from committing privileged work.
  • Single-component replacement stages and verifies a new runtime generation before making it active.
  • Multi-component replacement stages the complete generation and records progress for each component.
  • Multi-component start and stop honor dependency order.
  • KITPro retains the previous runtime generation when recovery may need it.
  • Cleanup failure is recorded as cleanup debt instead of changing a successful cutover into an ambiguous result.

Reconciliation and repair

  • Reconciliation classifies missing, stopped, drifted, unavailable, migrated, removed, and cleanup-pending runtime state.
  • Repair actions are explicit and bounded to trusted recorded state.
  • Runtime unavailable is distinct from runtime missing, so KITPro does not treat a temporary runtime outage as proof that resources disappeared.
  • KITPro can repair stale control projections from durable helper outcomes.
  • Migrated runtimes are handled without blindly repeating destructive work.
  • A deliberately removed runtime can become a stable reconciled state.
  • Exact orphan candidates can be cleaned without requiring an active generation.

Backup and restore

  • Restore uses a durable journal that records path identity, swap progress, generated secrets, prior runtime state, and cleanup debt.
  • Startup recovery can complete a proven forward state or roll back to the prior tree after a crash.
  • Mixed storage state fails closed when KITPro cannot prove a safe result.
  • Restore cleanup failures remain recorded for later cleanup or repair.

Migration

Alpha.11 schema 7 to alpha.12 schema 13 migration is supported and validated. Downgrading after this migration is unsupported.

Packages and checksums

File SHA-256
kitpro-server_0.1.0.alpha12_amd64.deb 29541da98fdba7fed0c4f7facec66d936c2da2487b8fedb562e289655fa8ac25
kitpro-debian-upgrade 8ddffc0070aec9576a7704a7b3f588ea7d0939dbed1c787a3c19ebcfd5489bb0
kitpro-server-0.1.0_alpha12-1-x86_64.pkg.tar.zst 2fe6b51c370c2e9399da9291c31ad2af6bb09934c1a872f502db0c8c615d12f6
kitpro-server-0.1.0_alpha12-1-upgrade.sh 0eab8578715fcaed71b27739036961e0e20fa48c5571a87e3351048513963f67
kitpro-server_0.1.0.alpha12_amd64.cdx.json 2f365f08afeb81c693ae7b4b0af59452b1220f08c432aa47a99a02a805bf6f27

Verify downloads against kitpro-alpha12-SHA256SUMS from this release.

Platform status

Debian and Arch Linux are the public supported baseline for this alpha. Rocky Linux and Podman-related work remain Experimental and are not promoted by this release.

Known limitations

  • This remains alpha software.
  • Runtime running state is not the same as application readiness.
  • Same-port replacement can have a bounded cutover interruption.
  • Failed restore or cleanup trees may require a later cleanup decision.
  • Some cleanup debt requires an explicit repair action.
  • Rocky Linux and Podman remain Experimental.
  • Downgrading after schema migration is unsupported.
  • KITPro does not provide arbitrary Compose management, generic container management, host-to-host restore, or rollback of irreversible application data migrations.

AI-assisted development

KITPro uses AI-assisted development tools within a human-directed engineering workflow. Project ownership, architecture, security decisions, review, validation, and release approval remain human responsibilities.