Skip to content

Latest commit

 

History

History
19 lines (14 loc) · 963 Bytes

RELEASE_PROCESS.md

File metadata and controls

19 lines (14 loc) · 963 Bytes
Raw

Release process

Releases are done automatically via GitHub actions and Release Drafter.

Rules

  1. Releases are only created from master.
  2. master is meant to be stable, so before tagging and create a new release, make sure that the CI checks pass.
  3. Releases are GitHub releases.
  4. Releases are following semantic versioning.
  5. Releases are to be named in pattern of X.Y.Z. The produced binary artifacts contain the X.Y.Z in their names.
  6. Changelog must up-to-date with what's going to be released. Check CHANGELOG.
  7. APP_VERSION file must be updated to match the draft version to be released (Please run the Pre Release action to create a PR update).

Flow

  1. Create a new GitHub release using https://github.com/go-nv/goenv
  2. Tag Version and Release Title are going to be in pattern of vX.Y.Z.
  3. Describe this release (content) is going to link the appropriate CHANGELOG entry.