Bump actions/github-script from 8.0.0 to 9.0.0

[dependabot]

Bumps actions/github-script from 8.0.0 to 9.0.0.

Release notes

Sourced from actions/github-script's releases.

v9.0.0

New features:

• getOctokit factory function — Available directly in the script context. Create additional authenticated Octokit clients with different tokens for multi-token workflows, GitHub App tokens, and cross-org access. See Creating additional clients with getOctokit for details and examples.
• Orchestration ID in user-agent — The ACTIONS_ORCHESTRATION_ID environment variable is automatically appended to the user-agent string for request tracing.

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.

What's Changed

• Add ACTIONS_ORCHESTRATION_ID to user-agent string by @​Copilot in actions/github-script#695
• ci: use deployment: false for integration test environments by @​salmanmkc in actions/github-script#712
• feat!: add getOctokit to script context, upgrade @​actions/github v9, @​octokit/core v7, and related packages by @​salmanmkc in actions/github-script#700

New Contributors

• @​Copilot made their first contribution in actions/github-script#695

Full Changelog: actions/github-script@v8.0.0...v9.0.0

Commits

• 3a2844b Merge pull request #700 from actions/salmanmkc/expose-getoctokit + prepare re...
• ca10bbd fix: use @​octokit/core/types import for v7 compatibility
• 86e48e2 merge: incorporate main branch changes
• c108472 chore: rebuild dist for v9 upgrade and getOctokit factory
• afff112 Merge pull request #712 from actions/salmanmkc/deployment-false + fix user-ag...
• ff8117e ci: fix user-agent test to handle orchestration ID
• 81c6b78 ci: use deployment: false to suppress deployment noise from integration tests
• 3953caf docs: update README examples from @​v8 to @​v9, add getOctokit docs and v9 brea...
• c17d55b ci: add getOctokit integration test job
• a047196 test: add getOctokit integration tests via callAsyncFunction
• Additional commits viewable in compare view

[github-actions]

🚀 Dogfood this PR with:

⚠️ WARNING: Do not do this without first carefully reviewing the code of this PR to satisfy yourself it is safe.

curl -fsSL https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.sh | bash -s -- 1279

Or

• Run remotely in PowerShell:

iex "& { $(irm https://raw.githubusercontent.com/CommunityToolkit/Aspire/main/eng/scripts/dogfood-pr.ps1) } 1279"

[Copilot]

Pull request overview

Updates GitHub Actions workflows in this repo to use actions/github-script v9.0.0 (from v8.0.0), aligning CI automation with the latest major release of the action.

Changes:

• Bump actions/github-script to v9.0.0 in remove-stale-label.yml.
• Update pinned actions/github-script commit SHA to the v9.0.0 release commit in dogfood-comment.yml and aspire-upgrade.lock.yml.

Show a summary per file

File	Description
.github/workflows/remove-stale-label.yml	Bumps actions/github-script to v9.0.0 for stale-label removal automation.
.github/workflows/dogfood-comment.yml	Updates the pinned actions/github-script SHA to v9.0.0 for PR dogfood comment automation.
.github/workflows/aspire-upgrade.lock.yml	Updates the pinned actions/github-script SHA to v9.0.0 across multiple gh-aw steps.

Copilot's findings

Comments suppressed due to low confidence (3)

.github/workflows/remove-stale-label.yml:34

• For issue_comment events on PRs, the payload typically doesn't include context.payload.pull_request.number; the PR number is available as context.payload.issue.number. Using context.payload.pull_request.number here will likely be undefined and cause removeLabel to fail. Use the issue number from the issue object for PR comments as well.

            github.rest.issues.removeLabel({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.payload.pull_request.number,
              name: 'stale'

.github/workflows/remove-stale-label.yml:35

• The github.rest.issues.removeLabel(...) call returns a promise but isn't awaited. That can cause the step to finish without surfacing API failures reliably (e.g., permission errors / missing label). Await the call so failures fail the workflow deterministically.

This issue also appears on line 42 of the same file.

            github.rest.issues.removeLabel({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.payload.pull_request.number,
              name: 'stale'
            });

.github/workflows/remove-stale-label.yml:47

• This github.rest.issues.removeLabel(...) call isn't awaited, so API failures may not be surfaced and the step can behave inconsistently. Await the promise so the workflow fails deterministically on errors.

            github.rest.issues.removeLabel({
              owner: context.repo.owner,
              repo: context.repo.repo,
              issue_number: context.payload.issue.number,
              name: 'stale'
            });

• Files reviewed: 3/3 changed files
• Comments generated: 0

[aaronpowell]

@dependabot rebase