Skip to content

MFA-Forge v0.1.20-rc.20

Pre-release
Pre-release

Choose a tag to compare

View all tags
@github-actions github-actions released this 08 May 05:00
v0.1.20-rc.20
This tag was signed with the committer’s verified signature.
wnunezc Walter Nuñez
GPG key ID: 1A9506A1E1CA15FC
Verified
Learn about vigilant mode.
22b2a22
This commit was signed with the committer’s verified signature.
wnunezc Walter Nuñez
GPG key ID: 1A9506A1E1CA15FC
Verified
Learn about vigilant mode.

MFA-Forge 0.1.20-rc.20

0.1.20-rc.20 closes the RC19 updater gap by restoring mfa-forge-launcher.exe to the installed MSI surface, adding an explicit GUI handoff for the next RC line, and validating the real RC19 -> RC20 upgrade path on the user installation with the published prerelease assets.

Scope

  • release line: RC20
  • numeric version: 0.1.20
  • RC tag: v0.1.20-rc.20
  • GitHub prerelease URL: https://github.com/wnunezc/MFA-Forge/releases/tag/v0.1.20-rc.20
  • MSI asset: MFA-Forge-RC20-x64.msi
  • checksum asset: MFA-Forge-RC20-x64.msi.sha256.txt

User-facing changes

  • the installed MSI now includes mfa-forge-launcher.exe
  • the GUI now exposes a deliberate Install next RC update action instead of implying any auto-update on app open
  • RC20 does not claim open MFA-Forge and it updates itself; the validated RC19 -> RC20 path is the RC20 MSI upgrade over the installed RC19 baseline

Engineering changes

  • workspace and package version advanced to 0.1.20
  • crates/gui/wix/main.wxs now packages mfa-forge-launcher.exe as an installed per-user binary
  • the GUI gained an explicit RC-update dialog that stages the next RC through the installed launcher
  • crates/cli/src/launcher.rs no longer carries RC18-specific prerelease copy in errors
  • release docs and architecture notes now distinguish the validated manual RC19 -> RC20 edge from the future launcher-driven path available after RC20 is installed

Validation evidence

Commands executed locally before publication:

  • pwsh -Command "cargo fmt --all -- --check"
  • pwsh -Command "cargo check --workspace"
  • pwsh -Command "cargo clippy --workspace --all-targets -- -D warnings"
  • pwsh -Command "cargo test --workspace"
  • pwsh -Command "cargo build --workspace --release"
  • pwsh -Command "cargo wix --package mfa-forge-gui --no-build --target-bin-dir target/release --output target/rc/MFA-Forge-RC20-x64.msi"
  • pwsh -Command "(Get-FileHash -LiteralPath 'target/rc/MFA-Forge-RC20-x64.msi' -Algorithm SHA256).Hash"

Manual findings captured during this RC20 pass:

  • baseline before the published-asset proof: C:/Users/wnune/AppData/Local/MFA-Forge/bin/ was restored to published RC19 (0.1.19) and did not contain mfa-forge-launcher.exe
  • exact public-asset upgrade command executed against the installed published RC19 baseline:
    • msiexec /i D:\OpsZone\DevWorkspace\Projects\Desktop\MFA-Forge\target\rc\published-rc20\MFA-Forge-RC20-x64.msi /passive /L*V D:\OpsZone\DevWorkspace\Projects\Desktop\MFA-Forge\target\rc\update-proof\msiexec-install-published-rc20-over-published-rc19.log
  • msiexec result: exit code 0
  • post-upgrade installed inventory now includes:
    • mfa-forge-gui.exe
    • mfa-forge-agent.exe
    • mfa-forge-mcp.exe
    • mfa-forge-launcher.exe
  • post-upgrade installed versions confirmed:
    • mfa-forge-gui.exe -> 0.1.20
    • mfa-forge-agent.exe -> 0.1.20
    • mfa-forge-mcp.exe -> 0.1.20
    • mfa-forge-launcher.exe -> 0.1.20
  • GUI smoke:
    • installed mfa-forge-gui.exe started successfully
    • process remained alive after 8s
    • CloseMainWindow() succeeded and the process exited with code 0
  • local surface smoke:
    • installed mfa-forge-mcp.exe answered initialize successfully
    • reported serverInfo.version = 0.1.20

Packaging evidence:

  • release build: target/release
  • local pre-publication MSI generation: target/rc/MFA-Forge-RC20-x64.msi
  • local pre-publication checksum generation: target/rc/MFA-Forge-RC20-x64.msi.sha256.txt
  • local pre-publication SHA256: 1BAAE242E1937100E8E313AA30AAEC4B5FE82823AD31DB464796DFC39B099007
  • published RC19 asset used as restored baseline: target/rc/published-rc19/MFA-Forge-RC19-x64.msi
  • published RC20 asset used for the final proof: target/rc/published-rc20/MFA-Forge-RC20-x64.msi
  • published RC20 checksum asset: target/rc/published-rc20/MFA-Forge-RC20-x64.msi.sha256.txt
  • published RC20 SHA256: 9B40572462B4699E5D8F720EC72A04E19002A55093E8FA762ABC8C265FBDF1E5
  • installed-upgrade log: target/rc/update-proof/msiexec-install-published-rc20-over-published-rc19.log
  • workflow run: https://github.com/wnunezc/MFA-Forge/actions/runs/25537176391

Release truth for RC20

  • validated path for the user installation today: manual MSI upgrade from published installed RC19 to published RC20
  • launcher-driven path for future RCs: available only after RC20 is installed, because RC20 is the first installed line in this arc that actually ships mfa-forge-launcher.exe
  • startup auto-update on GUI open: not implemented and not claimed
  • important packaging note: the workflow-produced public MSI differs from the pre-publication local MSI, so the final proof and checksum evidence for RC20 are anchored to the published release assets
Assets 4
Loading