Fix release action #160
Merged
Fix release action #160
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
jfhbrook
force-pushed
the
fix-release-action
branch
from
c19c7b3 to
9ffb736
Compare
|
Leroy Jenkins |
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.
ActionLint was reporting that the action I was using to create a GitHub release was deprecated. So, I went back to the drawing board.
First, I found a fork of the origin GitHub release action, and I slapped that in place. It has significant differences from the one I was using, namely that it didn't support uploading files. So I then followed this blog post and manually added the files with the
ghCLI.Of course, now I'm wondering if the blessed path is, in fact, to use the CLI to create the release.