From 951ed33a355d6fb8c259a700375568d7c8f3b65b Mon Sep 17 00:00:00 2001 From: Arun Sathiya Date: Thu, 1 Feb 2024 13:15:15 -0800 Subject: [PATCH] ci: Use GITHUB_OUTPUT envvar instead of set-output command (#276) `save-state` and `set-output` commands used in GitHub Actions are deprecated and [GitHub recommends using environment files](https://github.blog/changelog/2023-07-24-github-actions-update-on-save-state-and-set-output-commands/). 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 Co-authored-by: Wei Li --- .github/workflows/build_pypi.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.github/workflows/build_pypi.yml b/.github/workflows/build_pypi.yml index 5e5c5781..81318d24 100644 --- a/.github/workflows/build_pypi.yml +++ b/.github/workflows/build_pypi.yml @@ -56,7 +56,7 @@ jobs: run: | if [[ "${{ github.event_name }}" == "push" ]] && \ [[ "${{ github.event.ref }}" =~ ^refs/tags/v[0-9]+\.[0-9]+\.[0-9]+$ ]]; then - echo ::set-output name=match::true + echo "match=true" >> $GITHUB_OUTPUT fi - name: Upload to PyPI