Breaking changes:

• require('@actions/github') no longer works in scripts. The upgrade to @actions/github v9 (ESM-only) means require('@actions/github') will fail at runtime. If you previously used patterns like const { getOctokit } = require('@actions/github') to create secondary clients, use the new injected getOctokit function instead — it's available directly in the script context with no imports needed.
• getOctokit is now an injected function parameter. Scripts that declare const getOctokit = ... or let getOctokit = ... will get a SyntaxError because JavaScript does not allow const/let redeclaration of function parameters. Use the injected getOctokit directly, or use var getOctokit = ... if you need to redeclare it.
• If your script accesses other @actions/github internals beyond the standard github/octokit client, you may need to update those references for v9 compatibility.

@copilot do these breaking changes apply to the 4 uses of actions/github-script that are being used here?

Breaking changes:

• require('@actions/github') no longer works in scripts. The upgrade to @actions/github v9 (ESM-only) means require('@actions/github') will fail at runtime. If you previously used...

None of the breaking changes apply to the scripts in this repo. Checked all 10 uses across the 4 workflow files:

• No script uses require('@actions/github') — the one require() call (in pr_tests.yml) is for Node's built-in fs module, which is unaffected.
• No script redeclares getOctokit with const/let.
• All scripts already use the injected github, context, and core objects that v9 provides — they're compatible as-is.