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 command will be deprecated soon and upgrade to Node16. #55

Open
itsankit-google opened this issue Oct 14, 2022 · 7 comments
Open

Comments

@itsankit-google
Copy link

itsankit-google commented Oct 14, 2022

Describe the bug
Recently we started seeing these warnings on github actions -

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/

Warning: Node.js 12 actions are deprecated. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/. Please update the following actions to use Node.js 16: jitterbit/get-changed-files

Looks like the action is internally using set-output command which will be disabled soon by github.

To Reproduce
Steps to reproduce the behavior:

  1. Run a workflow using jitterbit/get-changed-files.

Expected behavior
Warning should not be seen.

Additional context
This action is really important for us and it is being used in an important workflow.

@dee-me-tree-or-love
Copy link

Following the blog post (one linked in the warning), it seems that the core.setOutput usage from '@actions/core' should be replaced with core.exportVariable. 🤔 I am not fully sure how to make this work without breaking changes though.

There is a related discussion in the actions/core here: actions/toolkit#1218

@zl-go
Copy link

zl-go commented Nov 8, 2022

i just use this action,but i can't see any output,are youfixxing this problem now or there is some problem?
image

@masesdevelopers
Copy link

For anyone interested in this issue we forked this repo into https://github.com/masesgroup/retrieve-changed-files and we solved the issue. We updated the name to be able to publish the action on marketplace too.
Until now it is still in testing phase on our public repositories (https://github.com/masesgroup/JNet, https://github.com/masesgroup/KNet), however the action masesgroup/retrieve-changed-files@v2 seems to solve the issue while maintains the behavior.

@pbek
Copy link

pbek commented Nov 22, 2022

Thank you!

@pbek
Copy link

pbek commented Nov 22, 2022

@masesdevelopers
Copy link

@pbek thanks for your feedback. Cert was renewed.

@os6sense
Copy link

Indeed, thank you @masesdevelopers

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

6 participants