chore(deps): bump actions/github-script from 8 to 9

[dependabot]

Bumps actions/github-script from 8 to 9.

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

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[github-actions]

📄 Terraform Plan DEV

-/+ destroy and then create replacement
-/+ resource "null_resource" "dummy" {
-/+ resource "null_resource" "dummy" {
Plan: 2 to add, 0 to change, 2 to destroy. 

Terraform used the selected providers to generate the following execution
plan. Resource actions are indicated with the following symbols:
-/+ destroy and then create replacement

Terraform will perform the following actions:

 # null_resource.dummy[0] must be replaced
-/+ resource "null_resource" "dummy" {
     ~ id       = "8370619634422548525" -> (known after apply)
     ~ triggers = { # forces replacement
         ~ "always_run" = "2026-03-30T14:33:53Z" -> (known after apply)
       }
   }

 # null_resource.dummy[1] must be replaced
-/+ resource "null_resource" "dummy" {
     ~ id       = "1966930584015184938" -> (known after apply)
     ~ triggers = { # forces replacement
         ~ "always_run" = "2026-03-30T14:33:53Z" -> (known after apply)
       }
   }

Plan: 2 to add, 0 to change, 2 to destroy.

View full plan

[github-actions]

✅ Terraform Apply DEV

Apply complete! Resources: 2 added, 0 changed, 2 destroyed. 

null_resource.dummy[1]: Destroying... [id=1966930584015184938]
null_resource.dummy[0]: Destroying... [id=8370619634422548525]
null_resource.dummy[0]: Destruction complete after 0s
null_resource.dummy[1]: Destruction complete after 0s
null_resource.dummy[0]: Creating...
null_resource.dummy[0]: Provisioning with 'local-exec'...
null_resource.dummy[0] (local-exec): Executing: ["/bin/sh" "-c" "echo 'Hello, Terraform! secret: 123'"]
null_resource.dummy[1]: Creating...
null_resource.dummy[0] (local-exec): Hello, Terraform! secret: 123
null_resource.dummy[0]: Creation complete after 0s [id=3004657941853945485]
null_resource.dummy[1]: Provisioning with 'local-exec'...
null_resource.dummy[1] (local-exec): Executing: ["/bin/sh" "-c" "echo 'Hello, Terraform! secret: 123'"]
null_resource.dummy[1] (local-exec): Hello, Terraform! secret: 123
null_resource.dummy[1]: Creation complete after 0s [id=4291420035996048951]

Apply complete! Resources: 2 added, 0 changed, 2 destroyed.

View full apply log