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

The set-output command is deprecated and will be disabled soon #36

Open
MZole opened this issue Oct 24, 2022 · 3 comments
Open

The set-output command is deprecated and will be disabled soon #36

MZole opened this issue Oct 24, 2022 · 3 comments

Comments

@MZole
Copy link

MZole commented Oct 24, 2022

The set-output command is deprecated and will be disabled soon.

We are using this workflow in one of our actions in this action. This action is referenced in our projects and it generates the warning for example on line 709 under Create Jira issues for community activities in the jobs.

@Piedone
Copy link

Piedone commented Nov 23, 2022

I see there's a new sheriff in Atlassian GitHub Actions town @mboudreau, and I'm really happy to see that! I'd ask you to please consider addressing this issue as well; it's similar housekeeping due to deprecation to the Node.js updates you've done.

@mboudreau
Copy link
Contributor

🤠

I'd love to fix this, however as per the blog, I've already updated @actions/core to the latest version as mentioned already in the latest release, but it's still showing the warning. This seems to be a problem within Github themselves - I think they're showing the message even though the runner hasn't updated to the latest version everywhere. My guess is is that this problem will subside ones the runners are updated globally.

@Piedone
Copy link

Piedone commented Nov 24, 2022

I see, thank you for your quick reply! We'll see what the maintainers reply there.

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

3 participants