Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

set-output is deprecated #5

Closed
mikestopcontinues opened this issue May 25, 2023 · 4 comments
Closed

set-output is deprecated #5

mikestopcontinues opened this issue May 25, 2023 · 4 comments

Comments

@mikestopcontinues
Copy link

I'm getting the following warning:

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 suspect the @github/actions package needs to be updated, since it seems set-output is being used under the hood.

@domi2120
Copy link
Contributor

@mikestopcontinues I'm not seeing this warning on any of my workflows using this action. The @actions/core package is currently on version 1.10.0 which should already contain a fix according to this comment and the release notes. Are you using the newest version of this action and sure that the warning is caused by it ?

@mikestopcontinues
Copy link
Author

I'm as confident as I can be. If I disable just the plugin, the warning disappears. (I just tried again.)

Is it possible one of the conditions in the comment aren't being met? In particular, does $GITHUB_OUTPUT need to be set manually in addition to core.setOutput()?

Here's the error:

Screenshot 2023-06-16 at 9 16 38 AM

Here's my config:

      - name: Lookup Last Success
        id: last-success
        uses: SamhammerAG/last-successful-build-action@v2
        with:
          branch: ${{github.ref_name}}
          workflow: ${{github.workflow}}
          token: ${{github.token}}
          verify: false

@domi2120
Copy link
Contributor

domi2120 commented Jun 16, 2023

@mikestopcontinues The Update of @actions/core to 1.10.0 was in version 3. Can you try using the current version (v4) and see if the warning still appears?

@mikestopcontinues
Copy link
Author

I'm sorry, @domi2120, I was just looking at the docs for the version number. It works now! Thanks for the help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants