Update and document release process #107
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
detiber
force-pushed
the
updateReleaseProcess
branch
from
56116a3
to
ed63b60
Compare
detiber
force-pushed
the
updateReleaseProcess
branch
from
ed63b60
to
a335e7e
Compare
mmlb
reviewed
Oct 1, 2021
detiber
force-pushed
the
updateReleaseProcess
branch
from
a335e7e
to
6b18f19
Compare
- Remove old tooling around bumping container image versions and publishing binaries - Add script to assist with tagging a release - Document the release process (push tag and github action that creates release)
detiber
force-pushed
the
updateReleaseProcess
branch
from
6b18f19
to
5de7489
Compare
detiber
commented
Oct 4, 2021
| @@ -0,0 +1,40 @@ | |||
| #!/usr/bin/env bash | |||
There was a problem hiding this comment.
@mmlb Did quite a bit of surgery on the script you referenced, but pretty happy with how it turned out.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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: