← Back to all articles

Phase Packages Now Include Integrity Verification

The Phase 1 Installer now checks server compatibility and SHA-256 file integrity before upgrades, downgrades, or repairs are applied.

Phase packages are now verified before installation

The Phase 1 Installer now validates server compatibility and SHA-256 file checksums before any managed file is written. A damaged, incomplete, or altered version package is rejected before the current installation is changed.

What changed

Added PHP version and extension compatibility checks.
Added SHA-256 checksums for every managed file in each phase package.
Added manifest identity validation after secure extraction.
Added an Installed Files verification tool.
Reports missing or modified managed files and identifies the correct repair package.
Keeps rollback snapshots and protected runtime data unchanged.

Why this matters

Version upgrades, downgrades, and reinstalls are now deterministic. Staff can verify the current installation, preview the target changes, and apply only a package that passes compatibility and integrity checks.

phase-1installerintegritysha256repairversions
Join the Discussion

Leave a comment

Comments are reviewed before appearing publicly.

Comments will return after the database migration is completed.
Discussion

Approved comments

0
No approved comments yet. Be the first to contribute.
Continue Reading

Related articles

Phase 1.22 Integrates the Version Manager Into the Dashboard

Upgrade, downgrade, repair, comparison, and verification tools now live inside the authenticated MineCave dashboard.

Installer Version Changes Can Now Be Previewed

Phase 1 now shows upgrade, downgrade, and reinstall file changes before the selected version is applied.

Phase 1 Introduces the Installer Version Library

Upgrades and downgrades now belong to the permanent Installer, with phase packages, rollback snapshots, protected runtime files, and downgrade cleanup.