chore(deps): bump anthropics/claude-code-action from 1.0.187 to 1.0.193

[dependabot]

Bumps anthropics/claude-code-action from 1.0.187 to 1.0.193.

Release notes

Sourced from anthropics/claude-code-action's releases.

v1.0.193

Full Changelog: anthropics/claude-code-action@v1.0.192...v1.0.193

v1.0.192

What's Changed

• fix(mcp): paginate GitHub Actions results by @​abhinavkr26104 in anthropics/claude-code-action#1629
• fix(summary): keep every text block in structured tool results by @​Neal006 in anthropics/claude-code-action#1619
• fix(mcp): detect binary files by content instead of extension allowlist by @​henriquepe in anthropics/claude-code-action#1633

New Contributors

• @​abhinavkr26104 made their first contribution in anthropics/claude-code-action#1629
• @​Neal006 made their first contribution in anthropics/claude-code-action#1619
• @​henriquepe made their first contribution in anthropics/claude-code-action#1633

Full Changelog: anthropics/claude-code-action@v1.0.191...v1.0.192

v1.0.191

Full Changelog: anthropics/claude-code-action@v1.0.190...v1.0.191

v1.0.190

Full Changelog: anthropics/claude-code-action@v1...v1.0.190

v1.0.189

Full Changelog: anthropics/claude-code-action@v1...v1.0.189

v1.0.188

What's Changed

• Enforce max-turn limits from claude_args by @​ulofiai in anthropics/claude-code-action#1607
• fix: handle null files field from GraphQL on very large PRs by @​leepokai in anthropics/claude-code-action#1593
• fix: support labeled action for pull_request events in track_progress by @​takakisatojp in anthropics/claude-code-action#1586
• fix: match label_trigger case-insensitively by @​sahilempire in anthropics/claude-code-action#1576
• docs: fix broken Bedrock anchor in cloud-providers.md by @​shoemoney in anthropics/claude-code-action#1579
• docs: replace removed base-action inputs with claude_args and settings by @​fallintoplace in anthropics/claude-code-action#1550
• fix(cache): disable setup-bun cache to avoid 5-retry HTML-error burn by @​necofuryai in anthropics/claude-code-action#1580
• ci: pass base-action tool restrictions through claude_args by @​fallintoplace in anthropics/claude-code-action#1552
• fix(mcp): stop retrying deterministic reference update failures by @​fallintoplace in anthropics/claude-code-action#1551
• fix: expose conclusion as a root action output by @​fallintoplace in anthropics/claude-code-action#1549
• fix(branch): validate generated branch name under commit signing by @​rishavnaskar in anthropics/claude-code-action#1582
• fix(branch): collapse empty path segments in branch_name_template by @​NickNojiri in anthropics/claude-code-action#1539

New Contributors

• @​ulofiai made their first contribution in anthropics/claude-code-action#1607
• @​leepokai made their first contribution in anthropics/claude-code-action#1593
• @​takakisatojp made their first contribution in anthropics/claude-code-action#1586
• @​sahilempire made their first contribution in anthropics/claude-code-action#1576
• @​shoemoney made their first contribution in anthropics/claude-code-action#1579
• @​fallintoplace made their first contribution in anthropics/claude-code-action#1550
• @​necofuryai made their first contribution in anthropics/claude-code-action#1580
• @​rishavnaskar made their first contribution in anthropics/claude-code-action#1582

... (truncated)

Commits

• 9d7150b chore: bump Claude Code to 2.1.233 and Agent SDK to 0.3.233
• e63208c chore: bump Claude Code to 2.1.232 and Agent SDK to 0.3.232
• dc33e8a chore: bump Claude Code to 2.1.231 and Agent SDK to 0.3.231
• c58ad32 chore: bump Claude Code to 2.1.229 and Agent SDK to 0.3.229
• dfb8fc7 fix(mcp): detect binary files by content instead of extension allowlist (#1633)
• a2489ef fix(summary): keep every text block in structured tool results (#1619)
• 8b87458 fix: paginate GitHub Actions MCP responses (#1629)
• 239e3a7 chore: bump Claude Code to 2.1.228 and Agent SDK to 0.3.228
• 5ef2e55 chore: bump Claude Code to 2.1.227 and Agent SDK to 0.3.227
• 6b082c4 chore: bump Claude Code to 2.1.226 and Agent SDK to 0.3.226
• 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]

Code Review

Pure Dependabot SHA bump of anthropics/claude-code-action (1.0.187 → 1.0.193) across 11 step references in 5 workflows. No blocking issues. Verification and one behavioral note below.

Verified

• SHA is authentic. 9d7150bc8a3dae8149739a88019d192b579ad90c is exactly what the annotated tag v1.0.193 dereferences to in anthropics/claude-code-action. The # v1 comment is preserved on every line.
• No stale references. All 11 occurrences of the old SHA (1623c367…) were replaced; nothing under .github/ or .claude/ still points at it.
• No removed inputs. Diffed action.yml between the two SHAs — the change is purely additive (new conclusion output, a no-cache: true flag on the internal setup-bun step, and a description tweak). Every input these workflows pass (anthropic_api_key, github_token, show_full_output, prompt, claude_args, allowed_non_write_users) still exists.
• No output regressions. No workflow here reads steps.*.outputs.* from an action step, so the new conclusion output is inert.
• No build/routing risk. Nothing touches src/config/products.js, docusaurus.config.js, sidebars/, or scripts/ — the KB copy pipeline and Docusaurus build are unaffected.
• No secret-handling changes. Secret plumbing and job permissions: blocks are untouched.

Behavioral change worth knowing about (not a defect in this PR)

Upstream #1607, included in v1.0.188, makes --max-turns in claude_args actually take effect. Previously it fell through to generic CLI pass-through; now parse-sdk-options.ts extracts it into sdkOptions.maxTurns, and run-claude-sdk.ts both caps the run and hard-throws if a "successful" result reports more turns than the cap.

Four steps in this repo pass --max-turns 50:

Workflow	Line	Step
.github/workflows/claude-issue-labeler.yml	230	content-fix
.github/workflows/claude-issue-labeler.yml	365	content-fix-followup
.github/workflows/claude-doc-pr.yml	205	Handle @claude request
.github/workflows/claude-code-followup.yml	90	Handle @claude request

A run that would previously have used, say, 70 turns now terminates with error_max_turns, which resolves to conclusion: failure and fails the step.

The consequence to watch is in claude-issue-labeler.yml: the Create PR and comment on issue steps at lines 232 and 367 are guarded only by if: steps.check-issue.outputs.issue_state == 'OPEN' && … — no always(). A failed preceding step therefore skips them. Since the content-fix skill pushes its branch itself, a run that hits the 50-turn cap after pushing would leave an orphan branch on the remote with no PR opened and no comment on the issue.

This is pre-existing workflow structure, not something the bump introduced, and it only bites if a content-fix run genuinely exceeds 50 turns. If that shows up in practice, the fix is to add continue-on-error: true to the action step and always() && to the PR-creation step's condition — worth a follow-up issue rather than blocking this bump. The vale-autofix.yml steps already use continue-on-error: true and don't set --max-turns, so they're unaffected either way.

The no-cache: true addition on setup-bun is a net win — it trades a 2–3s Bun download for the ~20–30s of doomed cache-retry burn described in the upstream comment.

Recommendation: safe to merge.