Action not adding artifact to release data
See original GitHub issueDescribe the bug I’m compiling LaTeX and using your action to get the artifact and then generate a release. The release is generated without a problem, but the artifact is never uploaded
To Reproduce My yaml configuration for your action is the following:
- uses: ncipollo/release-action@v1
with:
artifacts: main_v${{ needs.create_new_release_tag.outputs.new-tag }}
tag: "${{ needs.create_new_release_tag.outputs.new-tag }}"
commit: main
body: "New Release of documentation"
token: ${{ secrets.AUTO_RELEASE_TOKEN }}
The Artifact looks like this after being uploaded:
The release itself only contains the source, but not the main_v0.0.1
in this case
Expected behavior
The file main_v0.0.1
should be inserted into the newest release
Screenshots If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
- GitHub Action
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Create a Release and Upload Artifacts with GitHub Actions
Being able to automate release creation and artifact upload with GitHub Actions allows you to fully leverage continuous and automated delivery.
Read more >Release Artifacts in GitHub Actions - Mike Penz
Every build allows multiple artifacts to be uploaded, but please note that the name has to be unique, and will result in equally...
Read more >Upload a github action artifact to LATEST release
I started with github official action upload-release-asset to upload artifact. It requires a upload_url as an input which tells it the url of...
Read more >How to publish GitHub Actions artifacts by example
How? Just use the GitHub upload-artifact action. Steps to publish GitHub Action artifacts. A developer should follow these five steps to publish ......
Read more >Effectively Manage GitHub Actions Artifacts to Deploy Releases
The build artifact can now be accessed in another job in the workflow by being downloaded because you have a step to upload...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m preparing a release right now which will provide additional warning when an artifact isn’t found and support for tilde in the artifact path (for example if you are generating your artifacts somewhere like
~/builds
.Yes, you’re right, it was my misunderstanding because I understood the downloadable artifacts where the ones you meant, and assumed that I could just straight up connect them without anything fancy. I got it to work after that realization, thanks for your time!