Automate Releases

[nibanks]

Describe the feature you'd like supported

Right now, we document most of what we need to do in ./docs/Release.md, but it still is a chore to do it all manually. We should automate as much as possible.

Proposed solution

When a new tag is created, the internal, OneBranch pipelines should:

• Automatically publish the Linux packages
• Build the macOS artifacts
• Publish the build/test artifacts to the GitHub release that corresponds to the tag
• Create a PR to main to update the down-level test versions.

Additional context

No response

[polarathene]

Perhaps pin this for visibility? I was curious why new releases were being tagged but the GH releases were not publishing archives of the releases consistently.

You can look into some tools like GoReleaser that should integrate well into CI for the repo if your current pipeline is not well suited for keeping GH releases in sync with tagged releases?

[nibanks]

It's been on our to-do list for a while. Hopefully we can get to it soon.