Automate releasing new action versions - #274
Merged
maxim-lobanov merged 1 commit intoJun 30, 2021
Merged
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
maxim-lobanov
approved these changes
Jun 29, 2021
dmitry-shibanov
approved these changes
Jun 29, 2021
deining
pushed a commit
to deining/setup-node
that referenced
this pull request
Nov 9, 2023
* docs: update README.md [skip ci] * docs: update .all-contributorsrc [skip ci] Co-authored-by: allcontributors[bot] <46447321+allcontributors[bot]@users.noreply.github.com>
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
Reviewers
3 participants
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:
Currently, releasing new versions of the setup-node action is the manual and unreliable process. In scope of this PR we added a workflow file in order to automate creating/updating a major version tag when a new setup-node version is released. We use the actions/publish-action action for this purpose.
Details:
We added:
Reverting changes is almost the same process as updating major version tag. In case of any issues related to the updated tag, we have to manually trigger workflow run with the previous stable tag as a parameter.