Skip to content

Latest commit

 

History

History
25 lines (17 loc) · 669 Bytes

RELEASING.md

File metadata and controls

25 lines (17 loc) · 669 Bytes

Release Process

Pre-release

Create a pull request named Release v<version> to update the CHANGELOG.md:

  • Add a new header to representing the new release.
  • Consider adding a description for the new release. Especially if it adds new features or introduces breaking changes.

Release

  1. Add and push a signed tag:

    TAG='v<version>'
    COMMIT='<commit-sha>'
    git tag -s -m $TAG $TAG $COMMIT
    git push upstream $TAG
  2. Create a GitHib Release named v<version> with v<version> tag.

    The release description should include all the release notes from the CHANGELOG.md for this release.