Skip to content

chore(deps): update anthropics/claude-code-action digest to 2fee155 #1200

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
renovate wants to merge 1 commit into from
Closed

chore(deps): update anthropics/claude-code-action digest to 2fee155 #1200

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion .github/workflows/maint-76-claude-code-review.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -189,7 +189,7 @@ jobs:
- name: Run Claude Code Review
id: claude
continue-on-error: true
uses: anthropics/claude-code-action@51705da45eecce209d4700538bf8377d5b5fc695 # v1
uses: anthropics/claude-code-action@2fee15510437d71399d9139ed60433470484a8fb # v1

@coderabbitai coderabbitai Bot Jun 21, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🧹 Nitpick | 🔵 Trivial

Consider coordinating this update with linked repositories.

Based on the linked repositories context, both stranske/Workflows (template) and stranske/Template still reference the old commit hash 51705da45eecce209d4700538bf8377d5b5fc695 at line 192 of the same workflow file.

If this workflow is distributed as a template to consumer repositories, consider whether:

  1. This consumer repo is intentionally testing the new version first before rolling out to the template
  2. The template repositories should be updated simultaneously to maintain consistency
  3. There's a documented rollout process for action updates across the template ecosystem

This ensures all consumers benefit from the update and prevents version drift across repositories using the same workflow template.

🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/maint-76-claude-code-review.yml at line 192, The
anthropics/claude-code-action reference in this workflow file is being updated
to a new commit hash, but the linked template repositories stranske/Workflows
and stranske/Template still use the old commit hash
51705da45eecce209d4700538bf8377d5b5fc695. Ensure consistency across the template
ecosystem by either updating both the template repositories simultaneously to
use the new commit hash, documenting that this consumer repository is
intentionally testing the new version first before the templates are updated, or
deferring this update until the template repositories are ready. This prevents
version drift and ensures all template consumers have access to consistent
action versions.

Source: MCP tools

⚠️ Potential issue | 🔴 Critical | 🏗️ Heavy lift

Critical: Workflow integrity check will block this updated action from running.

The workflow-integrity check (lines 136-137) detects whether .github/workflows/maint-76-claude-code-review.yml has changed in the PR. Since this PR modifies line 192 of that exact file, the check will set workflow_unchanged=false, causing the condition on line 175 to fail and preventing the Claude review job from executing.

This creates a paradox: you cannot update the action hash without modifying the workflow file, but modifying the workflow file prevents the updated action from running in this PR. The new commit hash will merge but never actually execute until a subsequent PR that doesn't touch the workflow file.

Possible solutions:

  1. Temporarily disable or adjust the workflow-integrity check to allow action pin updates
  2. Accept that the updated action won't run in this PR and will only take effect in future PRs
  3. Exclude action pin updates (line 192 only) from the integrity check logic
🤖 Prompt for AI Agents 
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/maint-76-claude-code-review.yml at line 192, The
workflow-integrity check on lines 136-137 currently blocks the Claude review job
from running whenever any part of the workflow file changes, including the
action hash update on line 192. To fix this, modify the workflow-integrity check
logic to either exclude action pin updates from triggering the
workflow_unchanged=false state, or update the condition on line 175 to allow the
job to proceed when only the action reference on line 192 has been modified
without other substantive workflow changes. This allows action hash updates to
be verified and executed in the same PR without being blocked by the integrity
check.

with:
claude_code_oauth_token: ${{ secrets.CLAUDE_CODE_OAUTH_TOKEN }}
allowed_bots: '*'
Expand Down
Loading