ci: set output has been updated to use GITHUB_OUTPUT #1726 (#1727)

Co-authored-by: Lukasz Gornicki <[email protected]>
asyncapi · Jun 22, 2023 · 8e441e2 · 8e441e2
1 parent 86ffbb2
commit 8e441e2
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 3 deletions.
diff --git a/.github/workflows/lighthouse-ci.yml b/.github/workflows/lighthouse-ci.yml
@@ -32,7 +32,7 @@ jobs:
           )
         id: should_run
         name: Should Run
-        run: echo "::set-output name=shouldrun::true"
+        run: echo "shouldrun=true" >> $GITHUB_OUTPUT
         
       - if: steps.should_run.outputs.shouldrun == 'true'
         uses: actions/checkout@v3

diff --git a/pages/blog/automated-releases.md b/pages/blog/automated-releases.md
@@ -194,7 +194,9 @@ To share the output, you must assign an `id` to the step and declare a variable
 ```yaml
 - name: Get version from package.json after release step
   id: extractver
-  run: echo "::set-output name=version::$(npm run get-version --silent)"
+  run: |
+    version=$(npm run get-version --silent)
+    echo "version=$version" >> $GITHUB_OUTPUT
 ```
 
 You can access the shared value by the `id` and a variable name like `steps.extractver.outputs.version`. We use it, for example, in the condition that specifies if further steps of the workflow should be triggered or not. If the version in `package.json` changed after GitHub and NPM step, this means we should proceed with Docker publishing and pull request creation:
@@ -228,9 +230,14 @@ jobs:
           node-version: 13
       - name: Install dependencies
         run: npm ci
+        
       - name: Get version from package.json before release step
         id: initversion
-        run: echo "::set-output name=version::$(npm run get-version --silent)"
+        run: npm run get-version --silent
+
+      - name: Set output
+        run: echo "version=$(npm run get-version --silent)" >> $GITHUB_OUTPUT
+
       - name: Release to NPM and GitHub
         id: release
         env: