set-output deprecated

[neleshgoel]

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/

[imjohnbo]

Thanks for opening, @neleshgoel! I'm guessing this is referring to actions/toolkit#1218, since none of the example workflows use an explicit set-output but these lines in index.js use the setOutput function, which in turn seems to call set-output. Let me know if you see something different 🙏.

issue-bot/lib/issue-bot.js

Lines 459 to 471 in 512b3ba

	if (newIssueNumber) {
	core.info(`New issue number: ${newIssueNumber}`);
	core.setOutput('issue-number', String(newIssueNumber));
	}
	if (previousIssueNumber) {
	core.info(`Previous issue number: ${previousIssueNumber}`);
	core.setOutput('previous-issue-number', String(previousIssueNumber));
	}
	if (projectV2IssueItemId) {
	core.info(`Project V2 Issue Item Id: ${projectV2IssueItemId}`);
	core.setOutput('project-v2-issue-item-id', projectV2IssueItemId);

[sadikassistivlabs]

@imjohnbo does that PR I made to update @actions/core seem like it will fix this based on your analysis?