Repository navigation
Fenix 0.1.4 — security and manifest consistency
Security maintenance and runtime manifest consistency for the standalone Steam installer and Flightdeck integration.
- Include patched ZIP, rustls and certificate-verification dependencies.
- Keep runtime-helper destination hashes identical to the actual integration payload. Refuse inconsistent root/variant metadata before building a release.
- Retain prior upgrade/restore identities and existing Wine/DXVK/Windows payloads.
This supersedes 0.1.3, withdrawn from stable updates after its stale prefix-helper checksum was caught in Flightdeck's real archive upgrade test. Use 0.1.4.
Requires Flightdeck 0.3.5 or newer; installer contract 2 remains unchanged. No new full-flight or FenixSystem memory qualification is claimed.
Validation: all four PR CI jobs, Rust 1.98 workspace tests, static installer validation and strict Clippy/fmt pass. The exact candidate ZIP upgrades all four supported runners through Flightdeck in disposable profiles while retaining original runner files and add-on sentinels. All five final-main assets are byte-identical to that candidate. Complete corresponding sources and notices included.
If you manually tried the withdrawn 0.1.3 installer and it reports a changed Fenix dependency, use Restore original profile before installing 0.1.4. Restoration retains the replaced profile separately. Direct upgrade validation covers the preceding stable 0.1.2 release; an automatic migration from inconsistent 0.1.3 prefix metadata is not claimed.