MergeWarden v0.5.1
v0.5.0 shipped working agent-detection defaults. One of them did not work.
Claude Code appends this footer to a pull request body:
🤖 Generated with [Claude Code](https://claude.com/claude-code)
The product name sits inside a Markdown link, and body markers are matched as case-insensitive substrings — so the default Generated with Claude Code could never match a real body. It came from the scan study's search query, and GitHub's search index tokenises, so the query finds these pull requests even though a literal match does not.
Measured against 13 real Claude Code pull requests from the study corpus:
| Marker | Matches |
|---|---|
Generated with Claude Code (v0.5.0 default) |
0 of 13 |
Generated with [Claude Code] (v0.5.1 default) |
12 of 13 |
The one miss had its footer edited out before merge. Nothing detects that from the artifact, and the docs do not claim otherwise.
Why this marker carries more weight than the others: Codex, Cursor, Copilot and Devin open pull requests from their own bot accounts or branch prefixes, so authors and branch_patterns catch them. Claude Code usually runs on a developer's own machine and pushes to an ordinary branch name — so for that cohort the footer is frequently the only signal there is.
Also in this release
The scan study's methodology now states which of its rates carry across engine versions. The per-rule boundary rates (3.9%, 12.9%, 17.5%, 22.1%) are unaffected by v0.5.0's detection fix — verified by re-scanning a 66-PR stratified sample of the dataset under the new defaults, which produced identical boundary findings on 66 of 66. The "at least one finding" rate is a boundary-crossing rate and is not comparable to a v0.5.0+ run.
Upgrading
- uses: sjh9714/mergewarden@v0.5.1No configuration change required. A repository that sets body_patterns explicitly is unaffected; if you copied the old value, change it to ["Generated with [Claude Code]"].
Full notes: docs/release-notes-v0.5.1.md
Published from signed tag v0.5.1 (verified=true) with npm provenance.