Release Process

• During development

  • Make sure CHANGELOG.md is kept up-to-date with high-level, technical, but user-focused list of changes according to keepachangelog
  • Bump UNRELEASED version in CHANGELOG.md according to semver

• To release

  • Check version to be released is also correct in all hydra- software components, e.g. .cabal files
  • Replace UNRELEASED with a date in ISO8601
  • Create a signed, annotated git tag of the version: git tag -as <version>
  • (ideally) Use the released changes as annotation

• Note on non hydra- components

  • This monorepo contains also other packages which may be released independently
  • Individual CHANGELOG.md files are used, e.g. plutus-merkle-tree/CHANGELOG.md
  • Signed, annotated git tag with full package name + version shall be used, e.g. git tag -as plutus-merkle-tree-0.1.0