chore(deps): bump anthropics/claude-code-action from 1.0.189 to 1.0.193 - #1853
chore(deps): bump anthropics/claude-code-action from 1.0.189 to 1.0.193#1853dependabot[bot] wants to merge 1 commit into
Conversation
….0.189 -> 1.0.193 (head 741bb02)
…batch Extends this batch from four PRs to nine so the whole stale Dependabot backlog lands as one CI run and one staging verification, per the project policy on consolidating staging sweeps onto a single pinned candidate. Taken as-is (their commits are merged above, SHAs preserved): - #1791 modernc.org/sqlite 1.55.0 -> 1.56.0 (packages/vm-agent) - #1853 anthropics/claude-code-action 1.0.189 -> 1.0.193 SHA 9d7150bc verified to be the commit v1.0.193 dereferences to. Applied by hand, because each needed a second half Dependabot cannot see: - #1855 cloudflare/sandbox 0.12.1 -> 0.12.7. This supersedes the 0.12.5 already on this branch (from the now-closed #1792). Dependabot only rewrites the FROM digest, so the npm client and the reviewed-source-tag comment were moved with it. Digest re-verified against the Docker Hub manifest rather than trusted from the PR body. The governance test added by this batch is what forces these three to move together. - #1856 react 19.2.7 -> 19.2.8, @types/react 19.2.17 -> 19.2.18. Dependabot groups react with @types/react but NOT react-dom, which ships from the same repo and must match react exactly. Left alone it would have landed react 19.2.8 against react-dom 19.2.7. Bumped react-dom to 19.2.8 as well and recorded the reason in pnpm-workspace.yaml, mirroring the existing typescript-eslint lockstep comment directly above it. - #1854 @commitlint/config-conventional 21.2.0 -> 21.2.2. Same shape: @commitlint/cli is released in lockstep and 21.2.2 exists, so both moved. - #1857 wrangler 4.118.0 -> 4.123.0 (catalog). All npm versions confirmed present on the registry before pinning. `pnpm quality:dependency-governance` passes 6/6, including the image<->SDK exact-pin invariant now asserting 0.12.7 on both sides.
Bumps [anthropics/claude-code-action](https://github.com/anthropics/claude-code-action) from 1.0.189 to 1.0.193. - [Release notes](https://github.com/anthropics/claude-code-action/releases) - [Commits](anthropics/claude-code-action@6b082c4...9d7150b) --- updated-dependencies: - dependency-name: anthropics/claude-code-action dependency-version: 1.0.193 dependency-type: direct:production update-type: version-update:semver-patch ... Signed-off-by: dependabot[bot] <support@github.com>
741bb02 to
6fbc440
Compare
|
|
Superseded by #1909 (claude-code-action 1.0.189→1.0.200, which includes the changes from this PR's 1.0.189→1.0.193 bump). |
|
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. |



Summary
Validation
Staging Verification (REQUIRED for all code changes — merge-blocking)
Staging Verification Evidence
N/A: no runtime application code changes. Staging is also explicitly out of scope for the 2026-08-24 PR-board cleanup task.
UI Compliance Checklist (Required for UI changes)
N/A: no UI files changed.
End-to-End Verification (Required for multi-component changes)
N/A: single GitHub Actions workflow dependency pin.
Data Flow Trace
N/A: no application data flow changed.
Untested Gaps
N/A: full relevant validation is GitHub CI for the workflow dependency update.
Post-Mortem (Required for bug fix PRs)
N/A: not a bug fix.
Specialist Review Evidence (Required for agent-authored PRs)
N/A: Dependabot-authored PR. No local specialist subagents were used because no application code was changed.
Exceptions (If any)
Agent Preflight (Required)
Classification
External References
Official documentation and release notes for anthropics/claude-code-action: https://github.com/anthropics/claude-code-action/releases
Codebase Impact Analysis
Scope is .github/workflows/claude.yml only. The change updates the pinned action SHA for the Claude workflow and does not affect app runtime code.
Documentation & Specs
N/A: no public docs or specs need updates for a GitHub Actions dependency pin.
Constitution & Risk Check
Checked Principle XI for hardcoded values. The pinned action SHA is intentional supply-chain pinning in a workflow file. Main risk is workflow behavior drift in the external action, covered by fresh CI before merge.