New "set-output" command

[rez1dent3]

Describe the bug
After reading the article, I began to update my github actions. But now there is a problem with escaping the string. Something like this already happened here: #267

To Reproduce
Steps to reproduce the behavior:

          OUTPUT="${OUTPUT//$'\n'/'%0A'}"
          OUTPUT="${OUTPUT//$'\r'/'%0D'}"
-         echo "::set-output name=stdout::$OUTPUT"
+         echo "stdout=$OUTPUT" >> $GITHUB_OUTPUT

Diff: https://github.com/bavix/laravel-wallet-benchmark/pull/33/files

Expected behavior
Hyphenation characters will be displayed correctly.

Expected table: bavix/laravel-wallet-benchmark#32 (comment)
Actual table: bavix/laravel-wallet-benchmark#33 (comment)

---

Do I understand correctly that now escaping is automatic and crutches at the github actions level are no longer needed?

[xt0rted]

I ran into this yesterday while updating some of my workflows. The fix was to remove the escape code, it's no longer needed. If your value might span multiple lines then you need to write it out like this https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#multiline-strings

[rez1dent3]

Hello, @xt0rted . Thanks, I'll try later. Most likely this will solve the problem. I created an issue to report a possible mass issue.

[rez1dent3]

-        OUTPUT="${OUTPUT//'%'/'%25'}"
-        OUTPUT="${OUTPUT//$'\n'/'%0A'}"
-        OUTPUT="${OUTPUT//$'\r'/'%0D'}"
-        echo "::set-output name=stdout::$OUTPUT"
+        echo "stdout<<EOF" >> $GITHUB_OUTPUT
+        echo "$OUTPUT" >> $GITHUB_OUTPUT
+        echo 'EOF' >> $GITHUB_OUTPUT

@xt0rted Yes you are right. Thank you.