Repository navigation
Helix Boot v0.7.6
·
219 commits
to f236627d3fed0deb16f2860585120764fb8e502d
since this release
Added
- A stick a virtual machine also holds isn't written. Two systems writing one stick corrupts it. On Linux,
install.sh,refresh.sh,check.sh,theme.shand the window stop when a running libvirt VM has the stick attached as a disk, and warn when a VM is set to take it at its next start. scripts/vm-stick.sh give <vm>/take <vm>hands the stick to a running VM and takes it back: unmounted here before it is attached there, and mounted here again only after it is detached. Nothing is added to the VM's settings.
Fixed
- The app's window opens in the middle of the screen. Where Windows put it on a small screen, the bottom row of buttons could be under the taskbar.
Changed
- What has been tried on real hardware, and what hasn't.
scripts/release.shwaits for CI on the commit it is about to release, and stops if a run failed or was cancelled.- CI downloads and verifies every tool (about 4 GB) on the weekly run, for a release, and when
helix,tools.tomlor the workflow changed. Any other push skips that, and still asks every upstream for its latest. - ProduKey is off by default. Windows Defender stops it being written, so a new stick no longer meets that. Tick it in the app's Tools window (or enable it in
local.toml) to have it. Without that, the next update from the PC that put it on a stick takes it off again, as for any tool that is no longer chosen; a stick filled by another PC keeps it.
Checking a download: sha256sum -c SHA256SUMS, or gh attestation verify HelixBoot.exe --repo Commanderx-code/helix-boot.
Full Changelog: v0.7.5...v0.7.6