Hi — heads-up on a hard upstream deadline that affects this action.

Issue

anthropics/claude-code-action pins oven-sh/setup-bun@3d267786b128fe76c2f16a390aa2448b815359f3 (v2.1.2) at two locations:

• action.yml line 176
• base-action/action.yml line 100

Both pinned instances use bun-version: 1.3.6.

setup-bun v2.1.2 uses Node.js 20. GitHub has announced that Node.js 20 actions will be forced to Node.js 24 on June 2, 2026. Current runner annotation:

"Node.js 20 actions are deprecated. … Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026."

Proposed fix

Bump both setup-bun pins to v2.2.0 or later. Per setup-bun's release notes, v2.2.0 (2026-03-14) updates the action runtime to Node.js 24 (PR #176 on oven-sh/setup-bun). This is the minimum version that survives the June 2 removal.

Context

We consume anthropics/claude-code-action in a downstream workflow (Claude PR Code Review). Our repo does not pin setup-bun directly, so we cannot work around the deprecation on our end — the fix has to land upstream.

Verification

$ gh api /repos/anthropics/claude-code-action/contents/action.yml | jq -r '.content' | base64 -d | grep -n "setup-bun"
176:        uses: oven-sh/setup-bun@3d267786b128fe76c2f16a390aa2448b815359f3 # v2.1.2

$ gh api /repos/oven-sh/setup-bun/releases | jq -r '.[] | select(.tag_name == "v2.2.0") | {tag: .tag_name, date: .published_at}'
{
  "tag": "v2.2.0",
  "date": "2026-03-14T..."
}

Happy to submit a PR if that helps — this is a 2-line change (one SHA bump at each pin location + version comment update). Let me know.

Thanks.