[CI/CD] Update automatic release action to actively maintained one #1207
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
taysta
force-pushed
the
openjk-autorelease
branch
from
05ca1c4 to
075a5c2
Compare
taysta
force-pushed
the
openjk-autorelease
branch
from
075a5c2 to
51657e7
Compare
ensiform
approved these changes
Nov 12, 2024
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.
https://github.com/marvinpinto/action-automatic-releases is currently used to download the artifacts and to create the "latest" release. It is in an abandoned state using Node 12 and will stop working entirely quite soon.
https://github.com/softprops/action-gh-release is an actively maintained action that achieves the same purpose. It is likely going to have a v2 soon, which will include a bump to Node 20, which has already been committed (as Node 16 depreciation warnings have now begun on actions).
Known problem with this runner:
It successfully uploads the artifacts and creates the latest release, if a latest release exists, it re-uploads the files to that pre-existing release, instead of re-creating the "latest" release as the current action does. I have only tested this on v1 so far, and will shortly run some tests to see if this behavior persists on the latest commit of the action.
Update:
https://github.com/crowbarmaster/GH-Automatic-Releases is a suitable replacement, it functions 1:1 to the previous implementation and has already been updated to Node 20.