Remove old tooling around bumping container image versions and publishing binaries
Document the release process (push tag and github action that creates release)
Why is this needed
Previous process was undocumented and did not match up with the existing state of the repository
How are existing users impacted? What migration steps/scripts do we need?
This may affect users who were relying on binaries to be published as part of a sandbox release, but after discussing with @jacobweinstock, we are not aware of any users that are relying on the published binaries.
If it turns out that there are folks that were consuming the binaries, we can re-introduce the tooling around publishing binaries as part of the release.
Checklist:
I have:
[x] updated the documentation and/or roadmap (if required)
Description
Update and document release process
Why is this needed
Previous process was undocumented and did not match up with the existing state of the repository
How are existing users impacted? What migration steps/scripts do we need?
This may affect users who were relying on binaries to be published as part of a sandbox release, but after discussing with @jacobweinstock, we are not aware of any users that are relying on the published binaries.
If it turns out that there are folks that were consuming the binaries, we can re-introduce the tooling around publishing binaries as part of the release.
Checklist:
I have: