Release 0.6.0

[AlfredoG87]

Problem

We need to release 0.6.0 version

Solution

Version to be released --> newVersion = v0.6.0
Next version to be developed --> nextVersion = v0.7.0

Please refer to documentation on release details.

• Create the next Milestone nextVersion if it does not already exists, define the dates (release cadence) every sprint
• Ensure all tickets related to Milestone newVersion are completed. (except this one "release"). Is possible to move some to the next Milestone if deemed necessary.
• Ensure that all PRs have appropriate labels, milestone set and assignes.
• Trigger GHA Release Automation WF with newVersion-rc1 using main branch. (this will kick-off the automation release process)
  • Verify TAG newVersion-rc1 was created in Block Node Tags
  • Verify Release for newVersion-rc1 was created on Releases. Publish as a Pre-Release
  • Verify a Version Bump PR was created fo nextVersion-SNAPSHOT was created against main branch
  • Review, Approve and Merge the above PR.
  • Verify a container image was created on GHCR packages of Block-Node for newVersion-rc1 version
  • Verify a new Helm Chart was created on GH-Pages of BlockNode for newVersion-rc1 version
  • Verify a new image was created with the version for the simulator
  • Verify a new Chart was created for the simulator
  • Test Deployment using created helm chart, verify is using the newVersion-rc1 version.

If All tests pass on newVersion-rc1 version proceed with GA version.

• Trigger GHA Release Automation WF with newVersion version using release branch: release/newVersion
  • Verify TAG newVersion was created in Block Node Tags
  • Verify Draft Release for newVersion was created on Releases. Do not publish yet.
  • Verify a container image was created on GHCR packages of Block-Node for newVersion version
  • Verify a new Helm Chart was created for the block node server.
  • Test Deployment using created helm chart, verify is using the newVersion version.
• Publish GA Release Version
  • Generate Release Notes using GH Template and Button.
  • Add a Summary to the Generated Notes that captures the highlights of the release
  • Publish Release as a latest version.
• Announce the release on Slack Channel of Block-Node.