We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
A workflow using save-state or set-output like the following
name: Save state run: echo "::save-state name={name}::{value}"
name: Set output run: echo "::set-output name={name}::{value}"
should be updated to write to the new GITHUB_STATE and GITHUB_OUTPUT environment files:
name: Save state run: echo "{name}={value}" >> $GITHUB_STATE
name: Set output run: echo "{name}={value}" >> $GITHUB_OUTPUT
=> Seems to be in docker/#-action@v1 and docker/metadata-action@v3 in
docker/#-action@v1
docker/metadata-action@v3
MetFragRelaunched/.github/workflows/docker-image.yml
Line 14 in f2b08d3
Line 26 in f2b08d3
=> Maybe there are newer ones ? Yours, Steffen
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
A workflow using save-state or set-output like the following
name: Save state
run: echo "::save-state name={name}::{value}"
name: Set output
run: echo "::set-output name={name}::{value}"
should be updated to write to the new GITHUB_STATE and GITHUB_OUTPUT environment files:
name: Save state
run: echo "{name}={value}" >> $GITHUB_STATE
name: Set output
run: echo "{name}={value}" >> $GITHUB_OUTPUT
=> Seems to be in
docker/#-action@v1
anddocker/metadata-action@v3
inMetFragRelaunched/.github/workflows/docker-image.yml
Line 14 in f2b08d3
and
MetFragRelaunched/.github/workflows/docker-image.yml
Line 26 in f2b08d3
=> Maybe there are newer ones ?
Yours,
Steffen
The text was updated successfully, but these errors were encountered: