Auto-releases

[ericbuckley]

Summary

Setup a process for automatically create releases upon events.

Acceptance Criteria

• Create a pre-release CI job, triggered on merges to main
• Create a release CI job, triggered on release tags

Details / Tasks

Creating a pre-release on merges

Every time we merge a PR into main, an action should kick off to create/update a pre-release. We can use an action like release-drafter or something similar for auto-generating the description of the Release. We should be comparing the HEAD on main to the last release tag, for calculating the differences. As for the name, please use the following syntax.
[YY.FF.BB]-rc.[CC]

• YY: the current 2 digit year
• FF: the next release for this calendar year (this should always be 1 more than the last release, the exception is when the year changes from the last release, in that case this should just be "01")
• BB: the bugfix number for this planned release, for pre-releases this should always be "00"
• CC: the number of commits to main since the last release

Creating a production release on new tags

When a new tag is added to main, that matches the vXX.XX.XX syntax, rename the existing pre-release title to match the new tag format.

Background / Context

Our tagging process loosely fits the CalVer system.