Release 0.8.1

Release checklist

Before finalizing release

Make these changes in the main branch before releasing:

• Ensure all applications/dependencies/charts are at their latest versions (#1175 (closed)) see .gitlab/issue_templates/update_all_components.md
• Trigger CI upgrade test from last release version to main by creating a branch starting with pre-release and create a MR for this

In the pre-release merge request

• Update CHANGELOG.md
• Include all merged MR since last release, i.e. using lab: lab mr list -s merged -a | awk '{first = $1; $1=""; print "*" $0, "(" first ")"}'
  • Include app charts and versions table (Use tablemark-cli): helm ls -A -o json | jq 'map({name, chart, app_version})' | jq 'map(.chart |= split("-")[-1])' > /tmp/versions.json tablemark /tmp/versions.json
  • Include Known issues
• Update the version number in the VERSION file
• Commit (signed)
• Push to MR
• Make sure the MR pipeline (including the upgrade pipline) is successful before merging MR !
• Wait for MR to get merged

Push a signed tag

• Make sure the main pipeline succeeds for the last commit before tagging. This is important because tags should not get retagged !
• Create and push signed tag (git tag -s 0.8.2 -m 'Release 0.8.2'; git push --tags)
• Create a new MR to merge the release branch into main (!961 (merged))
• If this is a major release, create a new release branch (i.e. v0.9)

After release

• Log into https://readthedocs.org and update documentation for tagged versions
• Create an issue for creating a release blog post
• Create an issue for cleaning up
  • old branches
• Celebrate 🥂 !!