Add save-state and set-output file commands by rentziass · Pull Request #1178 · actions/toolkit (original) (raw)

thboop

thboop

@rentziass

@rentziass

@rentziass

This was referenced

Oct 4, 2022

This was referenced

Oct 6, 2022

redian added a commit to redian/tar-action that referenced this pull request

Jan 5, 2023

@redian

In version 1.10.0 of @actions/core they have fixed the warning we are getting for set-output in our github actions.

As per per this PR actions/toolkit#1178 And as discussed here actions/toolkit#1218

This was referenced

Mar 16, 2023

skeggse

elliottkember added a commit to elliottkember/github-actions-query-branch-name that referenced this pull request

Jul 20, 2023

@elliottkember

levibostian added a commit to levibostian/decaf that referenced this pull request

Nov 26, 2024

@levibostian

When running the tool, I get 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/

But I'm using the latest 1.11.0 version of actions/core npm module so this shouldn't happen? I found the PR that implemented a fix for the deprecation, actions/toolkit#1178, and in it, I see that it checks if it has access to the GITHUB_OUTPUT environment variable. If it doesn't, it will fallback to previous behavior.

commit-id:c8c672a4

levibostian added a commit to levibostian/decaf that referenced this pull request

Nov 26, 2024

@levibostian

When running the tool, I get 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/

But I'm using the latest 1.11.0 version of actions/core npm module so this shouldn't happen? I found the PR that implemented a fix for the deprecation, actions/toolkit#1178, and in it, I see that it checks if it has access to the GITHUB_OUTPUT environment variable. If it doesn't, it will fallback to previous behavior.

commit-id:c8c672a4

levibostian added a commit to levibostian/decaf that referenced this pull request

Nov 26, 2024

@levibostian

When running the tool, I get 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/

But I'm using the latest 1.11.0 version of actions/core npm module so this shouldn't happen? I found the PR that implemented a fix for the deprecation, actions/toolkit#1178, and in it, I see that it checks if it has access to the GITHUB_OUTPUT environment variable. If it doesn't, it will fallback to previous behavior.

commit-id:c8c672a4

levibostian added a commit to levibostian/decaf that referenced this pull request

Nov 28, 2024

@levibostian

When running the tool, I get 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/

But I'm using the latest 1.11.0 version of actions/core npm module so this shouldn't happen? I found the PR that implemented a fix for the deprecation, actions/toolkit#1178, and in it, I see that it checks if it has access to the GITHUB_OUTPUT environment variable. If it doesn't, it will fallback to previous behavior.

commit-id:c8c672a4

levibostian added a commit to levibostian/decaf that referenced this pull request

Feb 17, 2025

@levibostian

When running the tool, I get 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/

But I'm using the latest 1.11.0 version of actions/core npm module so this shouldn't happen? I found the PR that implemented a fix for the deprecation, actions/toolkit#1178, and in it, I see that it checks if it has access to the GITHUB_OUTPUT environment variable. If it doesn't, it will fallback to previous behavior.

commit-id:c8c672a4

chhe pushed a commit to chhe/act_runner that referenced this pull request

May 1, 2026

@bircni

This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.Learn more about bidirectional Unicode characters

[ Show hidden characters]({{ revealButtonHref }})