New version: RedEyeNetworks.Logivore version 0.12.1

[beadams987]

Logivore v0.12.1 — first stable since the v0.11.0 SKU split. Adopts Argus multi-vendor malware pre-submission, restores the launch path that had silently broken across every build since v0.11.0 (DI registration regression on ILLMProvider), and unships the single-file Windows publish layout in favor of the PowerToys / Notepad++ multi-file shape (apphost + sibling DLLs) to defeat PAN WildFire's packed-binary ML signature that was quarantining v0.10.x → v0.12.0 on Cortex XDR endpoints.

4-installer shape unchanged from earlier published versions (0.10.1, 0.11.0): user-scope + machine-scope × x64 + arm64, each Inno Setup EXE wrapped around a multi-file self-contained .NET 9 publish. Azure Trusted Signing on every binary.

Manifest composed during the v0.12.1 release pipeline run (run #25890457211, 2026-05-14) and pulled from the CI artifact; submission is being driven manually for this version because the previous workflow_dispatch + submit_to_winget=true gate prevented auto-submission. Future stable tags will auto-submit per redeyenetworks/logivore#449.

Previous Logivore versions on Microsoft Store / WinGet: 0.10.1 (#368676 merged), 0.11.0 merged. v0.12.0 PR (#374296) was closed in favor of this current-stable submission to skip past a transient Microsoft-side validation-runner env glitch.

Microsoft Reviewers: Open in CodeFlow

[wingetbot]

Validation Pipeline Run WinGetSvc-Validation-142-374865-20260515-1

[wingetbot]

Publish pipeline succeeded for this Pull Request. Once you refresh your index, this change should be present.

[beadams987]

Closing — superseded by #374959 (New version: RedEyeNetworks.Logivore version 0.12.3), which carries the corrected version-stamping fix. v0.12.1 binaries reported 0.10.2-rc.1 to Add/Remove Programs metadata due to a release-pipeline regression where dotnet publish didn't get -p:Version= (every release from v0.10.2-rc.1 onward was affected). Fixed in redeyenetworks/logivore PR #450 + #456; v0.12.3 binaries now self-report 0.12.3 correctly, so any AppsAndFeaturesEntries.DisplayVersion mismatch question won't apply.