chore(deps): bump actions/github-script from 7 to 9#118
Closed
dependabot[bot] wants to merge 1 commit into
Closed
Conversation
Bumps [actions/github-script](https://github.com/actions/github-script) from 7 to 9. - [Release notes](https://github.com/actions/github-script/releases) - [Commits](actions/github-script@v7...v9) --- updated-dependencies: - dependency-name: actions/github-script dependency-version: '9' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
This was referenced Jun 18, 2026
Owner
|
Superseded by #131, which consolidates all open Dependabot updates into a single PR. Closing in favour of that. |
Contributor
Author
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
dependabot
Bot
deleted the
dependabot/github_actions/actions/github-script-9
branch
wiiiimm
added a commit
that referenced
this pull request
Jun 18, 2026
…r title] (#131) * chore(deps): consolidate open dependabot updates (GMC-45) Combine all 13 open Dependabot PRs (#116–#129) into a single update. npm group (#129): @octokit/graphql 9.0.3, apollo3-cache-persist 0.15.0, chalk 5.6.2, dotenv 17.4.2, fuse.js 7.4.2, react 19.2.7, @types/react 19.2.17, tsup 8.5.1, vitest 4.1.9. npm majors: typescript 6.0.3 (#128), @vitest/coverage-v8 4.1.8 (#127), semantic-release 25.0.5 (#126), ink-testing-library 4.0.0 (#125), env-paths 4.0.0 (#124), @types/node 25.9.2 (#123), open 11.0.0 (#122). GitHub Actions: setup-node v6 (#120), checkout v6 (#119), github-script v9 (#118), download-artifact v8 (#117), cache v5 (#116). Verified: typecheck (TS 6), build, and full test suite (456/456) all pass. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * ci: bump release workflow to Node 22 for semantic-release 25 (GMC-45) semantic-release 25 requires Node ^22.14.0 || >=24.10.0; the release workflow still set up Node 20, which would fail `npx semantic-release` on the next push to main. Bump all setup-node steps to Node 22 (LTS). Flagged by Cursor Bugbot (High) and Codex (P1) on PR #131. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * chore: raise Node floor to >=20 for env-paths 4 and open 11 (GMC-45) env-paths@4 and open@11 both declare engines.node ">=20", but the package still advertised ">=18", letting Node 18-19 users install a build that breaks at startup (env-paths) and on browser open (open). Align engines.node and the setup docs to >=20. Node 18 is already EOL. Flagged by Cursor Bugbot (Medium) on PR #131. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * build: migrate to @yao-pkg/pkg and target node20 binaries (GMC-45) vercel/pkg (pkg@5.8.1) is archived and only ships base binaries up to Node 18, so release binaries embedded a Node 18 runtime — incompatible with env-paths 4 / open 11 (Node 20+) after raising the engine floor. Switch to the maintained @yao-pkg/pkg fork and build node20 targets in both the build:binaries script and the release workflow. The packager needs Node 22 to run, which the release jobs already use. Flagged by Cursor Bugbot (High) on PR #131. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> * docs: note build:binaries requires Node 22+ for @yao-pkg/pkg (GMC-45) The CLI runtime engine stays at Node >=20, but @yao-pkg/pkg requires Node >=22 to run. Document this in the Packaging section so contributors on Node 20/21 know the binary build needs a newer Node, rather than raising engines.node and wrongly forcing end users onto Node 22. Addresses CodeRabbit engine-mismatch note on PR #131. The companion "Invalid Windows pkg target" finding is a false positive: pkg-fetch's toFancyPlatform aliases "windows" -> "win" during target parsing. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com> --------- Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps actions/github-script from 7 to 9.
Release notes
Sourced from actions/github-script's releases.
... (truncated)
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 this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)