Update actions/github-script action to v8

[renovate]

This PR contains the following updates:

Package	Type	Update	Change
actions/github-script	action	major	v7.0.1 -> v8.0.0

---

Release Notes

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

v8.0.0

Compare Source

v7.1.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ 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.

[github-actions]

This change updates the GitHub workflow for cleaning up build references by upgrading the actions/github-script dependency to a newer major version, ensuring compatibility with the latest features and security fixes while keeping the workflow stable.

Walkthrough

• Chore: Upgraded the actions/github-script action from v7.0.1 to v8.0.0 in the build-cleanup workflow.

_{Model: o4-mini | Prompt Tokens: 314 | Completion Tokens: 356}

[github-actions]

Here is supportive feedback on your code, powered by AI insights. Some suggestions may not suit every situation, so pick what works best for you. You guide the process while AI lends a helpful hand.
_{Model: o4-mini | Prompt Tokens: 724 | Completion Tokens: 2160}

[github-actions]

You’re pinning the action by its full commit SHA, which reduces readability and makes upgrades harder. It’s usually better to target the major version tag (e.g. @v8) or a full semver range to get non-breaking updates automatically. For example:

steps:
  - uses: actions/github-script@v8      # pulls latest v8.x.x
    with:
      script: |
        github.rest.git.deleteRef({
          owner: context.repo.owner,
          repo: context.repo.repo,
          ref: 'refs/heads/old-branch'
        })

[github-actions]

The inline comment for the version (# v8.0.0) is now out of sync with your SHA pin. Either update or remove it entirely to avoid confusion. If you switch to @v8 you can drop the comment, since it’s implied by the tag’s semantics.

[github-actions]

It’s safer to wrap the delete in a try/catch so that a missing ref (404) won’t fail the entire workflow. Here’s an example:

with:
  script: |
    try {
      await github.rest.git.deleteRef({
        owner: context.repo.owner,
        repo: context.repo.repo,
        ref: 'refs/heads/old-branch'
      })
      console.log('Ref deleted successfully')
    } catch (error) {
      if (error.status === 404) {
        console.log('Branch not found, skipping deletion')
      } else {
        throw error
      }
    }