Warning in workflow about set-output
See original GitHub issueSo when I use “::set-output”:
I have this warning:
The set-output
command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
I set my “output” in first job to be used in second job of my workflow:
I get the “VERSION” output:
Then after I updated my echo command to this: I don’t have 'Version" output:
So @jamesottaway @phishy can you please help me check which part is wrong?
Issue Analytics
- State:
- Created a year ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Warning in workflow about set-output · Issue #334 - GitHub
Description: Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files.
Read more >How to Fix the set-output GitHub Actions Deprecation Warning
If you have a GitHub Actions workflow that sets an output using echo ::set-output key=value , you have started to see an unhelpful...
Read more >Deprecating save-state and set-output commands
Starting 1st June 2023 workflows using save-state or set-output commands via stdout will fail with an error. Patching your actions and workflows.
Read more >How to Patch the Deprecated set-output in GitHub Workflows ...
Within the last week or so, I started noticing deprecation warnings in the logs of my GitHub Actions workflow runs.
Read more >Github Actions: set-output does not seem to work
output1 is defined as that job's steps.step1.outputs.test . You can see a (very) minimal example of this here, with its corresponding workflow ......
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@christina-30 there’s no visible reason for the warning to appear, please address the issue to the team of the runner repo - they could provide more efficient support for the question.
@christina-30
The problem is with pwsh used as a shell for the step. To access the env. variable from it it is necessary to use $Env:VAR syntax. See here.
Thus the corrected step should look like:
Sample build.
Please confirm i understood your problem right and it is solved.