question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Warning Output from GitHub Actions

See original GitHub issue

Troubleshooting

Before submitting a bug report please read the Troubleshooting doc.

Behaviour

Warning: The `save-state` 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/

As per https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

Action authors who are using the toolkit should update the @actions/core package to v1.10.0 or greater to get the updated saveState and setOutput functions.

I can see the latest v3 release (v3.1.1) uses @actions/core@^1.9.0 https://github.com/docker/build-push-action/blob/v3.1.1/package.json#L31, and master has already been updated to @actions/core@^1.10.0 via https://github.com/docker/build-push-action/pull/695

Steps to reproduce this issue

  1. use docker/build-push-action@v3 to build an image

Expected behaviour

Tell us what should happen

No warnings

Actual behaviour

Tell us what happens instead

Warning output from GitHub Actions

Configuration

  • Repository URL (if public):
  • Build URL (if public):
      - name: Build Container
        id: build
        uses: docker/build-push-action@v3
        with:
          file: Containerfile
          context: .
          platforms: linux/${{ matrix.platform }}
          load: true
          tags: |
            container:latest

Logs

Download the log file of your build and attach it to this issue.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:6 (3 by maintainers)

github_iconTop GitHub Comments

1reaction
crazy-maxcommented, Oct 12, 2022

Should be good with latest release

0reactions
crazy-maxcommented, Oct 19, 2022

Frustratingly the actions UI doesn’t specify which one causes it

You can find out which step generates a warning by clicking on it.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Workflow commands for GitHub Actions
Creates a warning message and prints the message to the log. This message will create an annotation, which can associate the message with...
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.
Read more >
How to Patch the Deprecated set-output in GitHub Workflows ...
All five GitHub Actions that I maintain were using the set-output workflow command, mainly for reporting status, which means that all users of ......
Read more >
Dealing with Set-Output Depreciation Warnings in Terraform ...
Dealing with Set-Output Depreciation Warnings in Terraform github-actions. I've got a build that is running terraform on github actions (I ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found