chore(deps): upgrade @actions/core & @actions/github

[tcely]

No description provided.

[qodo-code-review]

Review Summary by Qodo

Upgrade GitHub Actions dependencies and dev tooling

✨ Enhancement

Walkthroughs

Description

• Upgrade @actions/core from v1.11.1 to v3.0.0
• Upgrade @actions/github from v6.0.0 to v9.0.0
• Update multiple dev dependencies to latest versions
• Modernize tooling stack with major version bumps

Diagram

flowchart LR
  A["package.json"] -->|"@actions/core v1→v3"| B["Updated Dependencies"]
  A -->|"@actions/github v6→v9"| B
  A -->|"eslint v9→v10"| B
  A -->|"@typescript-eslint/parser v8"| B
  B -->|"Regenerate"| C["bun.lock"]

Loading

File Changes

1. package.json Dependencies +7/-7

Major version upgrades for core dependencies

• Upgraded @actions/core from ^1.11.1 to ^3.0.0
• Upgraded @actions/github from ^6.0.0 to ^9.0.0
• Upgraded scramjet from ^4.36.0 to ^4.0.0
• Updated dev dependencies including eslint (^9.21.0 to ^10.0.0), @typescript-eslint/parser (^8.57.0
 to ^8.0.0), eslint-plugin-github (^5.1.0 to ^6.0.0), and @octokit/webhooks-types (^7.6.1 to ^7.0.0)

package.json

---

2. bun.lock Dependencies +0/-0

Regenerate lock file for updated dependencies

• Regenerated lock file to reflect updated package.json dependencies
• Updated dependency resolution for all upgraded packages

bun.lock

---

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0)

1. Private @actions/github import ☑ 🐞 Bug ⛯ Reliability

Description

src/no-response.ts imports and types Octokit using the internal module path
'@actions/github/lib/utils' while package.json upgrades @actions/github to ^9.0.0. If the internal
layout/exports changed in v9, module resolution will fail and the action binary build/run will
break.

Code

package.json[29]

+    "@actions/github": "^9.0.0",

Evidence

The PR upgrades @actions/github to a new major version, while the code depends on a deep/internal
path within that package (and uses it for a public type). Deep imports are not part of the public
API contract and are the most likely to change during major upgrades, which would cause the build to
fail when resolving '@actions/github/lib/utils'.

package.json[27-31]
src/no-response.ts[1-12]
src/no-response.ts[34-41]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
`src/no-response.ts` imports `GitHub` from `@actions/github/lib/utils` (a deep/internal path) and uses it to type `octokit`. After upgrading `@actions/github` to a new major (`^9.0.0`), this internal path is at high risk of changing, which would break module resolution and fail the Bun compile step / action execution.
### Issue Context
- The code already constructs Octokit via the public API: `github.getOctokit(token)`.
- Only the *type* currently depends on the internal `GitHub` symbol.
### Fix Focus Areas
- src/no-response.ts[1-12]
- src/no-response.ts[34-41]
### Suggested change
- Delete: `import { GitHub } from '@actions/github/lib/utils'`
- Replace `octokit: InstanceType<typeof GitHub>` with a public type, e.g.:
- `octokit: ReturnType<typeof github.getOctokit>`
- or explicitly import a public Octokit type if available from `@actions/github` exports.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

ⓘ The new review experience is currently in Beta. Learn more