Skip to content

Latest commit

 

History

History
13 lines (12 loc) · 956 Bytes

RELEASING.md

File metadata and controls

13 lines (12 loc) · 956 Bytes
Raw

Releasing

  • Update the version number in lib/honeycomb/beeline/version.rb.
  • Update CHANGELOG.md with the changes since the last release. Consider automating with a command such as these two:
    • git log $(git describe --tags --abbrev=0)..HEAD --no-merges --oneline > new-in-this-release.log
    • git log --pretty='%C(green)%d%Creset- %s | %an'
  • Commit changes, push, and open a release preparation pull request for review.
  • Once the pull request is merged, fetch the updated main branch.
  • Apply a tag for the new version on the merged commit (e.g. git tag -a v2.3.1 -m "v2.3.1")
  • Push the tag upstream (this will kick off the release pipeline in CI) e.g. git push origin v2.3.1
  • Ensure that there is a draft GitHub release created as part of CI publish steps (this will also publish to Gems registry).
  • Click "generate release notes" in GitHub for full changelog notes and any new contributors
  • Publish the draft release in GitHub.