Attach a minisign signature (SHA256SUMS.minisig) to each release, made
from the MINISIGN_SECRET_KEY CI secret. The step no-ops (release stays
unsigned) when the secret isn't set, so releases don't break before it's
added; the upload skips the .minisig if it wasn't produced. README
documents verifying with the suite public key.
Attach a minisign signature (SHA256SUMS.minisig) to each release, made
from the MINISIGN_SECRET_KEY CI secret. The step no-ops (release stays
unsigned) when the secret isn't set, so releases don't break before it's
added; the upload skips the .minisig if it wasn't produced. README
documents verifying with the suite public key.
Attach a minisign signature (SHA256SUMS.minisig) to each release, made
from the MINISIGN_SECRET_KEY CI secret. The step no-ops (release stays
unsigned) when the secret isn't set, so releases don't break before it's
added; the upload skips the .minisig if it wasn't produced. README
documents verifying with the suite public key.
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.
Attach a minisign signature (SHA256SUMS.minisig) to each release, made
from the MINISIGN_SECRET_KEY CI secret. The step no-ops (release stays
unsigned) when the secret isn't set, so releases don't break before it's
added; the upload skips the .minisig if it wasn't produced. README
documents verifying with the suite public key.
9f2f6c886btocb559b188e