You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first-party create-release GitHub Action we are using has been archived since Mar 4, 2021. We should switch over to a third-party maintained action, the create-release README suggests a few candidates, or do away with the action entirely (using github-script similarly to python-tuf, perhaps).
The text was updated successfully, but these errors were encountered:
@joshuagl below mentioned alternative can be considered instead of create-release :
Release Drafter:
Release Drafter
Automatically drafts release notes from merged pull requests, streamlining the release process. then creating a release based on the draft created.
gh-action-create-release:
gh-action-create-release
Another community-supported option for creating GitHub releases and uploading associated assets.
If you like any one of the above-mentioned solutions , please let me know if I can work on this issue.
Thanks for your interest in working on this Shumham.
My personal preference is that we use only first party actions for the TUF repository and implement the relatively trivial amount of github-script ourselves for making a release (much like we did with python-tuf in cd.yml).
I'd be open to being convinced otherwise and happy to hear others' opinions.
The first-party create-release GitHub Action we are using has been archived since Mar 4, 2021. We should switch over to a third-party maintained action, the create-release README suggests a few candidates, or do away with the action entirely (using github-script similarly to python-tuf, perhaps).
The text was updated successfully, but these errors were encountered: