Release Automation

[huseyinbabal]

Description

Changes proposed in this pull request:

• Full automation is introduced to the release process
• This automation contains 2 main phases, Cut a new release and Finalize Release. Cut a new release is used once we decide to cut-off the main or release branch for a specific milestone. Finalize release is used to mark the release as stable once we verify everything in prerelease.

Code Freeze

Next Release Candidate

Once the release branch is pushed, it triggers a subsequent release candidate preparation that contains;

• Linter check
• Artifact generation (docker image, etc)
• Processing helm charts
• Change log generation

For example, once Helm charts are processed, changes are automatically pushed to the release branch. Here is some view of those.

Finalize Release

Once we verify everything in prereleases, we can just finalize the release.

Related issue(s)

Fixes #584
Documentation

[huseyinbabal]

I addressed all the items, now;

• There is v prefix for release tags
• We have release branches for minor and major releases. Multiple patch releases share same release branch
• Helm version in values yaml fixed
• skip-ci added for other required workflows
• Unused release scripts are removed
• .release file is removed

[mszostok]

I left additional comments, I will test that now on my fork now 👍

[huseyinbabal]

I left additional comments, I will test that now on my fork now 👍

Thanks, addressed them all, triggering jobs on my end too

[mszostok]

I was not able to do the patch release 😞
EDIT: my fault.

[huseyinbabal]

@mszostok addressed the items we discussed today

[mszostok]

my flow:

• Cut v0.55.0
  • we have v0.55.0-rc.1 ✅
• Introduce new change
  • we have v0.55.0-rc.2 ✅
• Click finalize release
  • we have v.0.52.0 ✅

All Helm charts looks good (image updated). Docker images are present in my ghcr.io

• Merge PR with patch to relaase-0.55
  • cutting next RC failed ❌ but there was a helpful message about cutting a dedicated patch release
• I cut the release for v0.55.1
  • we have v0.55.1-rc.1 ✅
• Click finalize release
  • we have v.0.55.1 ❓ ✅
  • but the job failed on pushing the tag https://github.com/mszostok/botkube/actions/runs/3141812407/jobs/5104685078
  • however the release was triggered properly: https://github.com/mszostok/botkube/actions/runs/3141817743

All Helm charts looks good (image updated). Docker images are present in my ghcr.io

LGTM 👍 a really nice job!

Before merging, please see my last comments:

• I saw that perms has changed for hack/process-chart.sh, any reason for that?
• why we have failed job for cutting the patch release: https://github.com/mszostok/botkube/actions/runs/3141812407/jobs/5104685078
  • fatal: tag 'v0.55.1' already exists. From my investigation, is a problem with process-chart which doesn't support skip-tagging properly.
  • related: Release Automation #751 (comment)
• Release Automation #751 (comment)