How to create a release

Pre-Release

• Make all necessary modification via a Pull request
• Ensure to change the emasser version
• Merge the pull request into the main branch
• A Draft release is generated with then next release number

NOTE: If the emasser version number is not changed, the RubyGem will not be published to the GitHub Package Registry (GPR) or to the RubyGems registry due to duplicate version not being allowed.

Release

• Go to the Releases page

• Click on the newly created Draft release button (the release numeric value)

• On the release pages click the edit button

• Ensure that the tile matches the tag version number

  • May need to create a new tag to match the release title

    

  • The release title is the release version number

    

• Change the comment blocks as needed (make sure What's New is the top block):

  • Replace the block title ## Features with ## What's New
  • Replace the block title ## Changes with ## What's Changed

• Make sure that the Set as the latest release checkbox is selected

• Click the Publish release button

  

Post-Release

• Verify that the following emasser package was generated and release to the appropriate registries:
  • RubyGems
  • DockeHub
• Verify that the latest release version is the one just created