Skip to content

Latest commit

 

History

History
12 lines (9 loc) · 994 Bytes

RELEASING.md

File metadata and controls

12 lines (9 loc) · 994 Bytes

In order to release a new version we need to draft a new release and tag the commit. Releases are following semantic versioning and specify major, minor and patch version.

Once release is published it will trigger corresponding Github Action based on the published release event. Release workflow will then proceed to build and publish all library artifacts to Maven Central.

Release requirements

  • tag should specify newly released library version that is following semantic versioning
  • tag and release name should match
  • release should contain the information about all the change sets that were included in the given release. We are using release-drafter to help automatically collect this information and generate automatic release notes.