-
Notifications
You must be signed in to change notification settings - Fork 373
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
Replace an unmaintained action #781
Replace an unmaintained action #781
Conversation
Added a solution for #780, though CI failure should be unrelated. |
57cdf42
to
291f536
Compare
@ahmetb Rebased, now ready to review! |
echo 'RELEASE_NOTES<<EOF' >> $GITHUB_ENV | ||
TAG=$GITHUB_REF_NAME hack/make-release-notes.sh >> $GITHUB_ENV | ||
echo 'EOF' >> $GITHUB_ENV |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks, do you mind explaining how this works. having trouble following along how we connect $GITHUB_ENV
to ${{ env.RELEASE_NOTES }}
below.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-environment-variable.
TL;DR we can set an env var by that way (we have to pass the release notes content to create_release
).
if: contains(github.ref, 'tags') | ||
uses: svenstaro/upload-release-action@v2 | ||
id: create_release | ||
uses: softprops/action-gh-release@v1 | ||
with: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can we also add fail_on_unmatched_files: true
(if not already set by default) as a safeguard?
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ahmetb, JohnTitor The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
The example release is here: https://github.com/2k36/krew/releases/tag/v0.100.2-rc.2
Note that the release body isn't rendered as Markdown since the latest release, opened #780 to track it.Fixed!This just replaces action with a new one, so nothing functional should have changed.
Fixes #776
Fixes #780