[BUG] Release workflow uses deprecated actions

[adambkaplan]

Is there an existing issue for this?

• I have searched the existing issues

Kubernetes Version

N/A

Shipwright Version

N/A

Current Behavior

The release workflow uses deprecated actions or commands. Notably:

1. create-release uses an EOL version of NodeJS
2. set-output command is deprecated.

Expected Behavior

Release workflow uses up to date actions.

Steps To Reproduce

N/A

Anything else?

• set-output deprecation: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
• NodeJS force upgrade: https://github.blog/changelog/2023-06-13-github-actions-all-actions-will-run-on-node16-instead-of-node12-by-default/

[jaydee029]

Hi, I'd like to work on this.

[adambkaplan]

@jaydee029 great! The workflow in question that we need to replace is in the .github directory linked here. If you find a similar workflow that appears to be well-maintained and kept up to date, please submit a pull request with your recommendation.

Otherwise you can write a script that uses the GitHub CLI (gh), which is available on all GitHub Actions runners. I believe this has commands which will let us draft releases.

[rxinui]

Hey @adambkaplan this does not seem to be relevant anymore

[adambkaplan]

It's still relevant - the referenced workflow is read-only: https://github.com/actions/create-release

[IrvingMg]

/assign @kaizakin

Working on the fix in #278.

[openshift-ci]

@IrvingMg: GitHub didn't allow me to assign the following users: kaizakin.

Note that only shipwright-io members with read permissions, repo collaborators and people who have commented on this issue/PR can be assigned. Additionally, issues/PRs can only have 10 assignees at the same time.
For more information please see the contributor guide

Details

In response to this:

/assign @kaizakin

Working on the fix in #278.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.