ci: Use GITHUB_OUTPUT envvar instead of set-output command (#219)

Financial-Times · Jan 25, 2024 · 38a2d04 · 38a2d04
1 parent 858396d
commit 38a2d04
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/.github/workflows/publish-to-npm-as-latest.yml b/.github/workflows/publish-to-npm-as-latest.yml
@@ -15,7 +15,7 @@ jobs:
     - run: npm ci
     - name: Get the version
       id: version
-      run: echo ::set-output name=VERSION::${GITHUB_REF/refs\/tags\//}
+      run: echo "VERSION=${GITHUB_REF/refs\/tags\//}" >> "$GITHUB_OUTPUT"
     - run: npm version --no-git-tag-version ${{ steps.version.outputs.VERSION }}
     - run: npm publish
       env:

diff --git a/.github/workflows/publish-to-npm-as-prerelease.yml b/.github/workflows/publish-to-npm-as-prerelease.yml
@@ -15,7 +15,7 @@ jobs:
     - run: npm ci
     - name: Get the version
       id: version
-      run: echo ::set-output name=VERSION::${GITHUB_REF/refs\/tags\//}
+      run: echo "VERSION=${GITHUB_REF/refs\/tags\//}" >> "$GITHUB_OUTPUT"
     - run: npm version --no-git-tag-version ${{ steps.version.outputs.VERSION }}
     - run: npm publish --tag prerelease
       env: