ci: Use GITHUB_OUTPUT envvar instead of set-output command

weaveworks / weave-gitops

Weave GitOps provides insights into your application deployments, and makes continuous delivery with GitOps easier to adopt and scale across your teams.

https://docs.gitops.weave.works/

Apache License 2.0

905 stars 151 forks source link

ci: Use GITHUB_OUTPUT envvar instead of set-output command #4190

Open arunsathiya opened 7 months ago

arunsathiya commented 7 months ago

save-state and set-output commands used in GitHub Actions are deprecated and GitHub recommends using environment files.

This PR updates the usage of set-output to $GITHUB_OUTPUT

Instructions for envvar usage from GitHub docs:

https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter