Skip to content

v0.3.0 — Autofix, token verification, legible errors

Choose a tag to compare

View all tags
@raphaelcm raphaelcm released this 10 Jul 20:32
· 14 commits to main since this release
v0.3.0
623d95f
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

What's new in v0.3.0

Autofix (on by default)

When a dependency bump breaks CI, a Claude agent drafts the small mechanical fix, bounds-checks it (a few lines, source only, never the manifest or .github/), and pushes it to the PR branch for you to review and merge — it never merges on its own. The injection-safe gate is untouched: an autofixed PR has source changes, so the whitelist keeps the deterministic gate from ever auto-merging it. Opt out with --no-autofix.

Install-time token verification

The installer now verifies your CLAUDE_CODE_OAUTH_TOKEN actually authenticates (a quick claude -p probe) before storing it, and re-prompts on failure. A wrong or expired token fails at install with a clear message instead of silently breaking the pipeline in CI hours later. (Setup-token OAuth tokens last ~a year; a copied keychain access token is short-lived and will expire.)

Real errors, surfaced

When a review or autofix run produces no result, the job now prints the agent's actual error — e.g. 401 Invalid bearer token — read from claude-code-action's execution log, instead of guessing "probably the App." The #1 cause, an invalid/expired token, is now legible at a glance, with the remedy.

Smoother install

  • Surfaces the required Claude Code GitHub App and opens the install page (the token alone isn't enough).
  • After writing the files, offers to commit + push, so "done" means live.

Model

Default review/fix model is claude-opus-4-8 (frontier Opus).

Full changelog: v0.2.0...v0.3.0

Assets 2
Loading