Repository navigation
Releases
v1.0.281
Claude Code GitHub Action v1.0
ð Claude Code GitHub Action v1.0 - Now Generally Available!
We're excited to announce the v1.0 release of Claude Code GitHub Action! This major release brings significant improvements in simplicity, flexibility, and power to AI-assisted development workflows.
ð What's New in v1.0
Simplified Configuration
- Automatic mode detection - No more manual
modeconfiguration. The action intelligently determines whether to run in interactive or automation mode based on your setup - Unified interface - All prompts now go through a single
promptinput, and all CLI options throughclaude_args - Better SDK alignment - Closer integration with the Claude Code CLI for a consistent experience
More Powerful & Flexible
- Direct access to all Claude Code CLI capabilities through
claude_args - Support for custom system prompts, tool configurations, and model selection
- Enhanced compatibility with AWS Bedrock and Google Vertex AI
â ïļ Breaking Changes
This release includes breaking changes from v0.x. Key deprecated inputs have been replaced with a cleaner, more intuitive API:
mode,direct_prompt,override_promptâ unifiedpromptinputcustom_instructions,model,allowed_tools,mcp_configâclaude_argswith CLI format- Other deprecated:
disallowed_tools,anthropic_model,trigger_phrase,timeout_minutes
ð Please review our Migration Guide for detailed upgrade instructions and examples.
ðĄ New Use Cases & Examples
Explore the expanded possibilities with v1.0! We've created comprehensive examples showcasing various workflows:
- Automated PR Reviews - Intelligent code review on every pull request
- CI Failure Fixes - Automatically diagnose and fix failing tests
- Issue Triage - Smart categorization and response to new issues
- Documentation Generation - Keep docs in sync with code changes
- Security Scanning - Proactive vulnerability detection
- And many more!
ð§ Check out all examples at github.com/anthropics/claude-code-action/tree/main/examples
ð Quick Start
# Interactive mode - responds to @claude mentions
- uses: anthropics/claude-code-action@v1
with:
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
# Automation mode - runs immediately with prompt
- uses: anthropics/claude-code-action@v1
with:
prompt: "Review this PR for security issues"
anthropic_api_key: ${{ secrets.ANTHROPIC_API_KEY }}
claude_args: |
--model claude-4-0-sonnet-20250805
--max-turns 10ð Resources
- Migration Guide - Step-by-step upgrade instructions
- Examples - Ready-to-use workflow templates
- Documentation - Complete setup and configuration guide
ð Thank You
Thank you to our beta users for your invaluable feedback that shaped this release. We're excited to see what you'll build with Claude Code GitHub Action v1.0!
v1.0.280
Full Changelog: v1.0.279...v1.0.280
v1.0.279
What's Changed
Other changes
- Use the default branch's config on pull requests from authors without write access by @mhegazy in #2088
- Skip images when a description or comment has been edited by @mhegazy in #2091
Full Changelog: v1.0.278...v1.0.279
v1.0.278
v1.0.277 (breaking changes)
What's Changed
â ïļ Breaking changes
Other changes
- Use the base branch's npm and Bun config on outside pull requests by @mhegazy in #2020
- Start Bun with the action's own tsconfig again by @mhegazy in #2058
- Close gaps in using the base branch's npm and Bun config by @mhegazy in #2026
- Keep deny rules that hold commas or parentheses by @mhegazy in #2033
Full Changelog: v1.0.276...v1.0.277
v1.0.276
Full Changelog: v1.0.275...v1.0.276
v1.0.275
v1.0.274
v1.0.273 (breaking changes)
What's Changed
â ïļ Breaking changes
- Deny code-running commands on PRs from authors without write access by @mhegazy in #2001
- Run sessions in auto mode by default by @mhegazy in #2004
- Keep the token out of .git/config when bots are allowed by @mhegazy in #2005
- Stop a session from leaving programs for later steps to run by @mhegazy in #2003
- Keep fork branch names away from this repository's branches by @mhegazy in #2007
- Stop forced pushes and file reads through the git allow rules by @mhegazy in #2006
- Only trust text and runs from the person who passed the write check by @mhegazy in #2002
Other changes
Full Changelog: v1.0.272...v1.0.273
â ïļ Upgrade notes: new security defaults
This release tightens what a Claude session can do, especially on content from people without write access. Workflows on @v1 get these changes automatically. Most keep working as they are, but check the items below if yours runs tests on outside pull requests, uses later steps after the action, or relies on --allowedTools as a strict list.
Sessions start in auto mode
A safety review now decides tool calls that no allow rule covers. Calls that used to be denied can run if the review passes, so --allowedTools is no longer a strict list. Workflows with a prompt can also edit workspace files without an allow rule.
Opt out: set the earlier mode in claude_args: --permission-mode acceptEdits for @claude mentions, or --permission-mode default for workflows with a prompt.
Sessions keep the earlier defaults if you set allowed_non_write_users, allowed_bots, a custom ANTHROPIC_BASE_URL or path_to_claude_code_executable. The same applies if your settings input is a file path, or sets a base URL or another permission mode.
Code-running commands are denied on outside pull requests
If a pull request's author doesn't have write access, common commands such as npm test and bun install are denied, even if claude_args allows them. The run still succeeds, so check the log for a warning.
Opt out: restrict_untrusted_prs: false. This lets code from that pull request run in a job that holds your workflow's tokens.
Only trusted text and runs start a session
- Slash commands and the trusted request come only from text the person who triggered the run wrote. Claude still reads a labeled or assigned issue's body for context.
- Editing or deleting someone else's comment or review no longer starts a run.
- With
promptandtrack_progress,label_triggerandassignee_triggernow apply. workflow_runalso checks the owner of the fork the run came from.- A run started by a bot's activity on a pull request also needs that pull request's author to have write access or be an allowed bot.
Adjust:
- If your workflow filters labels itself, set
label_triggerto your label, or to""to accept any label. - For
workflow_runon outside contributions, add those users toallowed_non_write_usersand passgithub_token.
There's no opt-out for the rest.
A session can't leave anything behind for later steps
GITHUB_ENV, GITHUB_PATH and git config are restored when the session ends, so a session's changes to them no longer reach later steps. Token revocation also ignores ~/.curlrc, including a proxy set there.
Git hooks are also off from before the checkout on pull requests covered by restrict_untrusted_prs, so a push Claude makes on one of those won't upload Git LFS objects.
Adjust: pass values to later steps with GITHUB_OUTPUT or --json-schema. There's no opt-out.
No token in .git/config when allowed_bots is set
These workflows now use the same credential helper as allowed_non_write_users, and it only answers for your GitHub server.
Adjust: a later step that pushes through origin, or fetches from it on a private repository, needs its own credentials: GH_TOKEN, GIT_ASKPASS, a credential saved for the username x-access-token, or its own remote URL. There's no opt-out.
Stricter git commands in @claude runs
- Commits go through a wrapper that rejects flags outside a short list, including
--amend,--no-verify,--authorand flags that read a file. - Pushes can't be forced and only update the branch the session was set up on: a new branch, or the open pull request's branch.
- A deny rule for
git commitorgit pushmust be inclaude_argsto cover these wrappers. One in a settings file doesn't.
Opt out: add your own rule in claude_args, such as Bash(git commit:*) or Bash(git push:*). This brings back what the wrappers block for that workflow.
Signed commits from prompt runs go to their own branch
With use_commit_signing, a run on an issue now commits to issue-N. A run on a pull request commits to its branch, or to pr-N if that branch isn't known to be in this repository. They used to reach the default branch or a branch named by a fork.
Opt out: set CLAUDE_BRANCH in the step's env to choose the branch.