update: docs + publish script for the self-update feature
README gets a top-level Updating section; docs/privileges.md gains a step-by-step trust-model writeup of `banger update`. The new scripts/publish-banger-release.sh drives the manual release cut: build, tar, sha256sum, cosign sign-blob, verify against the embedded public key, jq-merge into manifest.json, rclone upload to the R2 bucket. Refuses outright if the embedded key is still the placeholder so we can't accidentally publish an unverifiable release. Also folds in gofmt drift accumulated across the updater package and a few sibling files. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This commit is contained in:
parent
8ed351ea47
commit
fae28e3d8b
10 changed files with 310 additions and 33 deletions
|
|
@ -23,9 +23,9 @@ var expectedReleaseEntries = []string{
|
|||
// StagedRelease describes the result of unpacking a release tarball
|
||||
// into a staging directory.
|
||||
type StagedRelease struct {
|
||||
BangerPath string
|
||||
BangerdPath string
|
||||
VsockAgentPath string
|
||||
BangerPath string
|
||||
BangerdPath string
|
||||
VsockAgentPath string
|
||||
}
|
||||
|
||||
// StageTarball reads the gzipped tar at tarballPath and extracts the
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue