Bump actions/github-script from 8 to 9 in the github group#268
Conversation
Bumps the github group with 1 update: [actions/github-script](https://github.com/actions/github-script). Updates `actions/github-script` from 8 to 9 - [Release notes](https://github.com/actions/github-script/releases) - [Commits](actions/github-script@v8...v9) --- updated-dependencies: - dependency-name: actions/github-script dependency-version: '9' dependency-type: direct:production update-type: version-update:semver-major dependency-group: github ... Signed-off-by: dependabot[bot] <support@github.com>
rtibblesbot
left a comment
There was a problem hiding this comment.
Routine major-version bump for a GitHub Actions dependency; CI passes and no breaking changes apply.
Dependency Update Review
Package: actions/github-script v8 → v9
Semver risk: Major
Dependency type: GitHub Actions workflow step (CI-only)
CI status: Passing
Changelog Analysis
Sources consulted:
- Release notes v9.0.0 (included in PR body)
- Compare v8...v9
Breaking changes in v9:
require('@actions/github')no longer works —@actions/githubv9 is ESM-onlygetOctokitis now an injected function parameter —const/letredeclarations of it will throw aSyntaxError
New features:
getOctokitfactory function injected directly into script context (multi-token workflows)ACTIONS_ORCHESTRATION_IDappended to user-agent string
Security fixes: None noted.
Compatibility Assessment
The single usage in pr_build.yml (lines 34–45) uses only the injected github.rest.* context to call repos.listReleases. It does not use require('@actions/github') or declare/reference getOctokit — neither breaking change applies. No code changes were needed alongside this version bump.
- Project uses affected APIs: no
- Peer dependency changes: no
- Code changes required: no
- Prior failed attempts: no (no maintainer comments on this PR)
Recommendation
APPROVE — breaking changes don't affect this project's usage; CI confirms compatibility.
@rtibblesbot's comments are generated by an LLM, and should be evaluated accordingly
How was this generated?
Reviewed the pull request diff checking for:
- Correctness: bugs, edge cases, undocumented behavior, resource leaks, hardcoded values
- Design: unnecessary complexity, naming, readability, comment accuracy, redundant state
- Architecture: duplicated concerns, minimal interfaces, composition over inheritance
- Testing: behavior-based assertions, mocks only at hard boundaries, accurate coverage
- Completeness: missing dependencies, unupdated usages, i18n, accessibility, security
- Principles: DRY (same reason to change), SRP, Rule of Three (no premature abstraction)
- Checked CI status and linked issue acceptance criteria
- For UI changes: inspected screenshots for layout, visual completeness, and consistency
| - name: Get latest Kolibri release | ||
| id: get_latest_kolibri_release | ||
| uses: actions/github-script@v8 | ||
| uses: actions/github-script@v9 |
There was a problem hiding this comment.
praise: Script uses only the injected github.rest.* context — the clean pattern that v9 is designed around. Neither breaking change (ESM require, getOctokit redeclaration) touches this script.
rtibbles
left a comment
There was a problem hiding this comment.
No concerns from changelog, PR build still works!
Bumps the github group with 1 update: actions/github-script.
Updates
actions/github-scriptfrom 8 to 9Release notes
Sourced from actions/github-script's releases.
Commits
3a2844bMerge pull request #700 from actions/salmanmkc/expose-getoctokit + prepare re...ca10bbdfix: use@octokit/core/types import for v7 compatibility86e48e2merge: incorporate main branch changesc108472chore: rebuild dist for v9 upgrade and getOctokit factoryafff112Merge pull request #712 from actions/salmanmkc/deployment-false + fix user-ag...ff8117eci: fix user-agent test to handle orchestration ID81c6b78ci: use deployment: false to suppress deployment noise from integration tests3953cafdocs: update README examples from@v8to@v9, add getOctokit docs and v9 brea...c17d55bci: add getOctokit integration test joba047196test: add getOctokit integration tests via callAsyncFunctionDependabot 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 rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore <dependency name> major versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)@dependabot ignore <dependency name> minor versionwill close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)@dependabot ignore <dependency name>will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)@dependabot unignore <dependency name>will remove all of the ignore conditions of the specified dependency@dependabot unignore <dependency name> <ignore condition>will remove the ignore condition of the specified dependency and ignore conditions