-
I am running a shell script in an action and has the contents below
Will it be affected by the following change below? The GitHub BlogGitHub Actions: Deprecating set-env and add-path commands - GitHub ChangelogGitHub Actions: Deprecating set-env and add-path commands If so other than passing in arguments, what can be done? especially since I would really like to have $BUILD_TS The shell script… github.comais-one/vue-crud-x/blob/96e7850cdd12ec3272f99494b4bd92e72285fed2/example-app/deploy.sh
This file has been truncated. show original |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments
-
What you define there are variables, not environment variables. You also don’t echo |
Beta Was this translation helpful? Give feedback.
-
ok thanks, then it could be something else that was generating those warnings… I think I might have used something like $GCP_PROJECT_ID which is also set it github secrets… which caused this? I added link to the shell script file at the start of the topic |
Beta Was this translation helpful? Give feedback.
-
Many actions including official GitHub actions use outdated dependencies. Version 1.2.6 of Any action which uses an older version may cause a depreciation warning in the annotations of workflow runs. |
Beta Was this translation helpful? Give feedback.
Many actions including official GitHub actions use outdated dependencies.
Version 1.2.6 of
@actions/core
implements the new way of setting environment variables using a file. Action authors will have to update their dependencies.Any action which uses an older version may cause a depreciation warning in the annotations of workflow runs.