asset
output as a JSON array containing information about the uploaded assetsgenerate_release_notes
which when set to true will automatically generate release notes for you based on GitHub activity #179. Please see the GitHub docs for this feature for more informationGITHUB_TOKEN
resolution. GITHUB_TOKEN
is no resolved first from an env varibale and then from and input #133tag_name
#130This is a release catch up have a hiatus. Future releases will happen more frequently
files
input does not actually match what you expect #55repository
input, useful for creating a release in an external repository #61id
to outputs, useful for refering to release in workflow steps following the step that uses this action #60upload_url
as action output, useful for managing uploads separately #75target_commitish
value, useful to customize the default #76body_path
input first then fall back on body
input. this was the originally documented precedence but was implemened the the opposite order! #85url
output of this Action #28with: body_path
was not being used in generated GitHub releasesGitHub's api doesn't explicitly have a way of fetching a draft release by tag name which caused draft releases to appear as separate releases when used in a build matrix. This is now fixed.
GitHub actions inputs don't inherently support lists of things and one might like to append a list of files to include in a release. Previously this was possible using a comma-delimited list of asset path patterns to upload. You can now provide these as a newline delimieted list for better readability
- name: Release
uses: softprops/action-gh-release@v1
if: startsWith(github.ref, 'refs/tags/')
with:
files: |
filea.txt
fileb.txt
filec.txt
env:
GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
with.prerelease: true
#19You'll need to remove docker://
prefix and use the @v1
action tag