chore(deps): update actions/github-script action to v7

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/github-script	action	major	v6 -> v7

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

actions/github-script (actions/github-script)

v7

Compare Source

---

Configuration

📅 Schedule: Branch creation - "before 4am on Monday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Run Prettier check

Failed stage: Run Prettier [❌]

Failed test name: prettier:check

Failure summary: The action failed because the Prettier check found code style issues in the file .nuke/build.schema.json. The file does not comply with the formatting rules enforced by Prettier.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 477: �[36;1mnpm run prettier:check�[0m 478: shell: /usr/bin/bash -e {0} 479: ##[endgroup] 480: > [email protected] prettier:check 481: > prettier --check . --ignore-path .gitignore 482: Checking formatting... 483: [warn] .nuke/build.schema.json 484: [warn] Code style issues found in the above file. Forgot to run Prettier? 485: ##[error]Process completed with exit code 1.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.

[codiumai-pr-agent-pro]

PR-Agent was enabled for this repository. To continue using it, please link your git user with your CodiumAI identity here.

CI Failure Feedback 🧐

Action: Run TypeScript check

Failed stage: Run TypeScript types check [❌]

Failed test name: ts:check

Failure summary: The action failed because a TypeScript type error occurred during the ts:check script execution: In the file scripts/generate-pdf.ts at line 35, column 44, there is a type error (TS2322). The error indicates that the type "new" is not assignable to the expected type boolean | "shell" | undefined.

Relevant error logs: 1: ##[group]Operating System 2: Ubuntu ... 474: npm audit fix --force 475: Run `npm audit` for details. 476: ##[group]Run npm run ts:check 477: �[36;1mnpm run ts:check�[0m 478: shell: /usr/bin/bash -e {0} 479: ##[endgroup] 480: > [email protected] ts:check 481: > tsc --jsx preserve --skipLibCheck 482: ##[error]scripts/generate-pdf.ts(35,44): error TS2322: Type '"new"' is not assignable to type 'boolean | "shell" | undefined'. 483: ##[error]Process completed with exit code 2.

---

✨ CI feedback usage guide:

---

The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
The tool analyzes the failed checks and provides several feedbacks:

• Failed stage
• Failed test name
• Failure summary
• Relevant error logs

In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

/checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

Configuration options

• enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
• excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
• enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
• persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
• final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

See more information about the checks tool in the docs.