Skip to content

Briosa Installer 0.4.0

Latest

Choose a tag to compare

@github-actions github-actions released this 20 Oct 10:10
· 4 commits to main since this release
2897d8d

Briosa Installer 0.4.0 is a security update. It rebuilds the self-contained Installer, CLI, launcher and Windows setup with .NET runtime 10.0.13 (SDK 10.0.402). That replaces the 10.0.12 runtime bundled in Installer 0.3.0, which the .NET 10.0.13 security fixes apply to. This release also brings the Briosa brand v2 design to the app.

Update existing Installer installations to 0.4.0. Updating a system-wide .NET installation doesn't patch the runtime bundled in an older Installer.

What's changed

  • Patched .NET runtime. The bundled NETCore and WindowsDesktop runtimes move from 10.0.12 to 10.0.13 (#29).
  • Brand v2 (Caliper b).
    • A new void-tile icon for the app, launcher and shortcut that reads on both light and dark taskbars.
    • The Installer compact logo, drawn as vector artwork.
    • The v2 palette: void in dark mode, clean room in light mode.
    • The Scanline measurement-grid background, turned off in high contrast.
    • The Saira font license now ships in licenses/ (#31, #33).
  • Release validation. Release packaging now installs, verifies and repairs the published Server 0.9.2 packages for SA 2024.1.0508.5 and 2026.1.0529.7. It does this through the packaged CLI and a disposable signed catalog (#21, #23, #25). Signing uses tools pinned to Briosa v0.9.2 (#27).

Package management, sources, settings, CLI commands and SDK registration work as in 0.3.0. Existing settings and installed server packages carry over unchanged.

Assets and verification

The offline setup and the portable ZIP each come with an adjacent SHA-256 checksum, and the ZIP also has package provenance. First-party binaries, the shortcut script, setup and uninstaller carry timestamped Windows signatures from David Lucas. The release workflow builds source commit 2897d8d04b52a26843b337968640635e0cd40ef3.

Validation covers:

  • core/CLI tests and the WPF workflow smoke;
  • complete offline packaging;
  • installing the real Server 0.9.2 packages for both SA targets;
  • signed CLI and launcher checks;
  • signed catalog/package interoperability;
  • setup lifecycle checks.

These checks don't start SpatialAnalyzer or change SDK registration. The existing enterprise acceptance limitations still apply.

Full changelog