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.4 release in the UI, then this will kick of a workflow that will update the v0 tag to point to v0.0.4 (or create v0 if it doesn't exist yet). With the next release it does the same thing. If v0.0.5 is published then v0 will be updated to point to that.
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.4
release in the UI, then this will kick of a workflow that will update thev0
tag to point tov0.0.4
(or createv0
if it doesn't exist yet). With the next release it does the same thing. Ifv0.0.5
is published thenv0
will 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: