Skip to content

bolt.gives Desktop v1.0.1

Choose a tag to compare

@embire2 embire2 released this 02 Aug 13:15

bolt.gives Desktop v1.0.1

Desktop v1.0.1 introduces the first fail-closed Azure Artifact Signing release pipeline.

  • Signs the native executable, assembly and installer with the Azure Artifact Signing xmrgives profile
  • Applies RFC3161 SHA-256 timestamps before packaging or publication
  • Verifies pinned Microsoft Private Trust root and intermediate certificates in memory without mutating the CI certificate store
  • Rejects unsigned, hash-mismatched, unsupported or incompatible binaries
  • Publishes the installer checksum and update manifest only after signature verification
  • Marks the v1.0.1 update mandatory so installed Desktop v1.0.0 clients block coding until the verified installer is launched

The configured Azure certificate profile uses PrivateTrust. Its root is not trusted by Windows by default, so unmanaged devices may still show an unknown-publisher or SmartScreen warning even though CI verifies the Authenticode signature and timestamp. Public consumer trust requires an approved Azure PublicTrust profile.

v1.0.0 baseline

The first independent native Windows release replaces the retired Electron web wrapper.

  • Native C#/.NET 8 WPF/XAML product shell
  • Email code sign-in inside the app, with Windows-protected session storage
  • Restored local project and chat history
  • Native Chat, Workspace, editor, terminal, deployment, settings and token-balance surfaces
  • ChatGPT-5.6 SOL, Opus 4.8, Sonnet 5 and Fable 5 model switching without losing project context
  • WebView2 restricted to generated project Preview
  • Start Menu and Desktop shortcuts plus first-run taskbar pin guidance
  • SHA-256-verified, progress-reporting optional or mandatory auto updates

Existing Electron v3.4.2 installations require this one manual installer migration because the retired wrapper had no updater. Once native Desktop v1.0.0 is installed, future optional or mandatory Desktop updates are discovered and applied automatically after SHA-256 verification.