The release job signs SHA256SUMS with the suite's minisign key and
attaches SHA256SUMS.minisig, so a download can be verified offline
against the public key the README now documents. Without the
MINISIGN_SECRET_KEY secret -- on a fork, or before the key is added --
the release is unsigned and the notes say so. One key signs the
installer, migrate and cli.
The release job signs SHA256SUMS with the suite's minisign key and
attaches SHA256SUMS.minisig, so a download can be verified offline
against the public key the README now documents. Without the
MINISIGN_SECRET_KEY secret -- on a fork, or before the key is added --
the release is unsigned and the notes say so. One key signs the
installer, migrate and cli.
The release job signs SHA256SUMS with the suite's minisign key and
attaches SHA256SUMS.minisig, so a download can be verified offline
against the public key the README now documents. Without the
MINISIGN_SECRET_KEY secret -- on a fork, or before the key is added --
the release is unsigned and the notes say so. One key signs the
installer, migrate and cli.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The release job signs SHA256SUMS with the suite's minisign key and
attaches SHA256SUMS.minisig, so a download can be verified offline
against the public key the README now documents. Without the
MINISIGN_SECRET_KEY secret -- on a fork, or before the key is added --
the release is unsigned and the notes say so. One key signs the
installer, migrate and cli.