Skip to content

Commit

Permalink
Update automated-releases.md
Browse files Browse the repository at this point in the history
removed redundancy and fixed _ENV to _OUTPUT
  • Loading branch information
SumantxD authored May 30, 2023
1 parent fa3865e commit a692b3e
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions pages/blog/automated-releases.md
Original file line number Diff line number Diff line change
Expand Up @@ -195,8 +195,8 @@ To share the output, you must assign an `id` to the step and declare a variable
- name: Get version from package.json after release step
id: extractver
run: |
npm run get-version --silent
echo "version=$(npm run get-version --silent)" >> $GITHUB_ENV
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:
Expand Down

0 comments on commit a692b3e

Please sign in to comment.