Create an automated release workflow #80
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
- When a tag is created and pushed that has a v prefix: - Automatically generate release notes with github - Push the pre-built sha-based image with a new tag for the version - Automatically create a release in github - Updates the CI workflow to not run on tags with a v prefix
|
/assign @jacobweinstock |
Codecov Report
@@ Coverage Diff @@
## main #80 +/- ##
=======================================
Coverage 50.83% 50.83%
=======================================
Files 3 3
Lines 417 417
=======================================
Hits 212 212
Misses 174 174
Partials 31 31 Continue to review full report at Codecov.
|
9 tasks
displague
reviewed
Apr 19, 2022
| For version v0.x.y: | ||
|
|
||
| 1. Create the annotated tag | ||
| > NOTE: To use your GPG signature when pushing the tag, use `SIGN_TAG=1 ./contrib/tag-release.sh v0.x.y` instead) |
There was a problem hiding this comment.
I thought I asked this already, perhaps I have. Is there any technical reason we can't use GH's release UI?
displague
approved these changes
Apr 19, 2022
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
When a tag is created and pushed that has a v prefix:
Updates the CI workflow to not run on tags with a v prefix
I modeled this off the automated process we are currently using for the sandbox releases.
Why is this needed
How Has This Been Tested?
It's the same process as what has been merged to boots in tinkerbell/smee#234