Riley Mete 5bfa96a5b0

fix: allow leading underscore in branch names (valid per git-check-ref-format) (#1486) ...

Branch names starting with an underscore (e.g. _release/v1.2.3) are valid
per git check-ref-format but were rejected by validateBranchName's
first-character whitelist. Since setupBranch validates a PR's baseRefName
after checkout, the action failed on every open PR targeting such a
branch. A leading underscore carries no option-injection risk (only a
leading dash does, which is still rejected separately).

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

2026-07-15 20:27:12 -07:00

..

create-prompt

Use modern noreply email for co-author trailers (#1369)

2026-07-03 22:38:02 -07:00

entrypoints

chore: bump Claude Code to 2.1.211 and Agent SDK to 0.3.211

2026-07-15 23:10:52 +00:00

github

fix: allow leading underscore in branch names (valid per git-check-ref-format) (#1486)

2026-07-15 20:27:12 -07:00

mcp

Drop buffered inline comment when it is posted live (#1405) (#1412)

2026-07-03 22:37:36 -07:00

modes

fix(mcp): align allowed-tools parser with SDK option parser (#1373)

2026-06-13 22:49:34 -07:00

utils

fix: sanitize {{label}} in branch name templates (#1492)

2026-07-15 20:21:02 -07:00