Migrate uses of ::set-output in code-analyzer to setOutput.

[samueljseay]

All Submissions:

• Have you followed the WooCommerce Contributing guideline?
• Does your code follow the WordPress' coding standards?
• Have you checked to ensure there aren't other open Pull Requests for the same update/change?

Changes proposed in this Pull Request:

This is a final set of changes to migrate all uses of set-output to write to the GITHUB_OUTPUT file instead. To do that here we install @actions/core and call setOutput.

It should be noted that calling setOutput will still throw a set-output warning right now because that library actually writes to GITHUB_OUTPUT as well as calling set-output. See actions/toolkit#1218

• This PR is a very minor change/addition and does not require testing instructions (if checked you can ignore/remove the next section).

How to test the changes in this Pull Request:

I think the simplest way to test this is with some basic code modification of the calling functions that print out found changes.

1. Fork WooCommerce, setup actions. See Remove some usages of set-output #35799 for example

2. Don't merge this PR but instead, merge this slightly modified branch: https://github.com/woocommerce/woocommerce/tree/dev/test-ca-output This has the same setOutput code, but passes in some dummy change data.

3. When the CI check runs on your fork, see that it outputs some dummy information for all the lint checks.

FOR PR REVIEWER ONLY:

• I have reviewed that everything is sanitized/escaped appropriately for any SQL or XSS injection possibilities. I made sure Linting is not ignored or disabled.

[github-actions]

Test Results Summary

Commit SHA: 4615456

Test 🧪	Passed ✅	Failed 🚨	Broken 🚧	Skipped ⏭️	Unknown ❔	Total 📊	Duration ⏱️
API Tests	259	0	0	2	0	261	1m 2s
E2E Tests	187	0	0	6	0	193	13m 7s

---

To view the full API test report, click here.
To view the full E2E test report, click here.
To view all test reports, visit the WooCommerce Test Reports Dashboard.

[psealock]

This is a final set of changes to migrate all uses of set-output

I'm finding a few more instances of ::set-output in the codebase, otherwise these changes are looking good 🚢

[samueljseay]

@psealock those will just be the ones that haven't been merged in my other open PRs 😄