-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Draft releases erroring as "Malformed version" #38
Comments
Yep I'm having the same issue. |
@devedse Temporary solution is to pin the action to version 0.0.8, like this: - name: Download release asset
id: download_asset
uses: dsaltares/[email protected]
with:
token: ${{ secrets.GITHUB_TOKEN }}
version: ${{ needs.build.outputs.release_id }}
file: release_asset.jar
target: release_asset.jar |
Yep that's what I did as well. |
We have the same problem, workaround works. |
Merged
#40 will fix this bug |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Opening this as issue after suggested by author on #36 (comment)
This issue started happening once PR #36 got merged.
It seems that since we now assume a well-formed version as part of the
getRelease
function, it completely ignored the scenario where you may be downloading draft assets (which means release version is "untagged-XXX", for example:untagged-f8c3edf8af6344f60679
).What we experience now is a "Malformed version" error when attempting to download assets, as shown in the picture below.
Here is a sample that reflects how we do with drafts:
The text was updated successfully, but these errors were encountered: