Deprecation warning for `set-output` command

[mishina]

I've just found that the deprecation warning is displayed in the GitHub Actions workflows for eslint-plugin-import.

• https://github.com/import-js/eslint-plugin-import/actions/runs/3768297080/jobs/6406611863
  

  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 believe the following code in this repository has something to do with it, is that right?

actions/node/run/index.js

Lines 36 to 38 in d90a9d3

 } else if (arg.startsWith('::set-output name=cache-hit::')) { 
 	core.info(`hijacking core.setOutput output: ${arg}`); 
 	cacheHit = arg === '::set-output name=cache-hit::true'; 

actions/node/install/index.js

Lines 62 to 64 in 6c38ef6

 } else if (arg.startsWith('::set-output name=cache-hit::')) { 
 	core.info(`hijacking core.setOutput output: ${arg}`); 
 	cacheHit = arg === '::set-output name=cache-hit::true'; 

[Jordan Harband]

Yep, exactly right :-) i haven’t gotten around to fixing it yet because it’s not easy to test (without breaking hundreds of repos).

[Jordan Harband]

Altho in this case the warnings are actually because i haven’t updated the github core package past .10 - for the same reason (testing and breakage)

[Jordan Harband]

I believe 63baadd has fixed this.