Update command #80
No reviewers
rawdaGastan
Labels
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
geomind_code/my_hypervisor!80
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "development_update"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
#79
No checksum verification. The binary is downloaded over HTTPS and written directly to disk with no integrity check. If the release includes a checksums asset (common), you should verify the download against it
@ -0,0 +63,4 @@let asset = find_binary_asset(&release.assets)?;println!(If you want we can add a progress indicator (suggestion)
@ -0,0 +68,4 @@asset.name);let bytes = clientconsider a timeout here to not block forever
@ -0,0 +79,4 @@.await.context("failed to read download body")?;let current_exe = std::env::current_exe().context("failed to determine current binary path")?;can be unreliable on some platforms (e.g., if the binary was invoked via a symlink). If this is always Linux, it's generally fine via /proc/self/exe, but we can add a comment
The update command now includes
SHA256checksum verification of downloaded binaries. The release workflow(.forgejo/workflows/release.yaml)has been updated to generate and upload achecksums.txtasset alongside the binaries.Important: This branch must be merged before cutting the next release. Releases created from older workflow versions won't include checksums.txt, and the update command will print a warning and skip verification. The first release after this merge will be the first one with full integrity verification.