Skip to content

release: define guarantees of automated GitHub releases #226

@GaspardKirira

Description

@GaspardKirira

Clarify what automated releases are expected to provide:

  • artifacts or not
  • supported platforms
  • checksum/signing guarantees

Until fully reliable, document when manual releases are acceptable.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions