Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR reverts a small change introduced with 84f77c4 where setting the action's output has been changed from using
@actions/core
'ssetOutput
function to writing the output toprocess.env.GITHUB_OUTPUT
:actions-find-and-replace-string/index.js
Line 11 in 84f77c4
This is exactly how it's described in GitHub's blog announcing the deprecation: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/
However, this does not work for multiline outputs, as they now fail with an error similar to this:
In fact, the
@action/core
library provided by GitHub has been updated a few days before the deprecation was announced such thatsetOutput
uses the new file-based mechanism (and correctly handles multi-line outputs by using an EOF-delimiter based approach): actions/toolkit#1178This change is contained in
@action/core==1.10.0
, which is already being used by this action.Long story short: This PR reverts this change to use
setOutput
provided by@actions/core
again, which should fix issues with multi-line outputs.