Add checksum-verified release installers
This commit is contained in:
parent
47d16eb714
commit
cb8c4e6fd4
9 changed files with 477 additions and 15 deletions
|
|
@ -8,7 +8,7 @@ pre-releases intended for dogfood and controlled automation only.
|
|||
Release archives are built for:
|
||||
|
||||
- Linux x86_64
|
||||
- macOS
|
||||
- macOS x86_64 and arm64
|
||||
- Windows x86_64
|
||||
|
||||
The daemon and control CLI are supported as a single `geth` executable on those
|
||||
|
|
@ -65,6 +65,11 @@ For a tagged release:
|
|||
- CI must pass formatting, check, tests, and clippy.
|
||||
- Security workflows must pass or have an explicit documented exception.
|
||||
- Release archives must be built by `.github/workflows/release.yml`.
|
||||
- Every archive must have a published SHA-256 checksum, and the release must
|
||||
include `SHA256SUMS` plus the platform installer entrypoints.
|
||||
- Packaged archives must include README, docs, and license files.
|
||||
- Packaged binaries must be smoke-tested from the archive.
|
||||
- Packaged binaries must be checksum-verified and smoke-tested from the archive
|
||||
through the same installer path documented for users.
|
||||
- Installers must never initialize a home, create trust state, or start a user
|
||||
service; `geth daemon install` remains a separate explicit action.
|
||||
- Any breaking changes must be called out in release notes.
|
||||
|
|
|
|||
Loading…
Reference in a new issue