Add release action #208
Merged
Add release action #208
Conversation
This file contains hidden or 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
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.
Adding a new workflow similar to what we have in other first party actions to update tags whenever a new release is made. This is for non-immutable versions. Long term this will be removed.
For example, when we create a
v0.0.4release in the UI, then this will kick of a workflow that will update thev0tag to point tov0.0.4(or createv0if it doesn't exist yet). With the next release it does the same thing. Ifv0.0.5is published thenv0will be updated to point to that.This leverages this action that we are using: https://github.com/actions/publish-action
You can find examples of this exact thing in other first party actions: