Skip to content

Latest commit

 

History

History
8 lines (7 loc) · 572 Bytes

RELEASING.md

File metadata and controls

8 lines (7 loc) · 572 Bytes

Releasing

  1. A new version should be determined by following the semantic versioning scheme.
  2. Create a new branch called prepare-xx.xx.xx-release using the updated version number.
  3. Update the version number in the CHANGELOG and document all appropriate changes since the last release.
  4. Update the version number where appropriate in the README (if applicable).
  5. Create and merge a Pull Request for this branch.
  6. In GitHub, go to [https://github.com/livefront/sealed-enum/releases] and create a new release with "Draft a new release".