--configure-git sets a commit identity and installs SSH commit signing backed by a code-sign subcommand.
What's wrong with this entry?
--configure-git sets a git identity of Claude <[email protected]>, installs an SSH commit signing program and Co-authored-by hook stubs under <base-dir>/.runner, and requires git 2.34 or newer. The signing itself is done by a new self-hosted-runner code-sign subcommand, which sends the commit to the session's signing endpoint using the session access token.
--use-anthropic-git-proxyroutes clones through Anthropic's git proxy using a repo-local credential helper. It requires--capacity 1and git 2.32 or newer.- A governed-git configuration delivered by the server can supersede the proxy, mounting repos read-only and resetting
remote.origin.urlback to the plain upstream address. - Only SSH-style signing is supported by
code-sign; anything else is rejected.
code-sign: only SSH-style signing (-Y sign) is supported; got:
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.234
Self-hosted runners report when warm-up finished
Both mention self hosted runner
-
v2.1.236
Self-hosted runner releases a session only after its work finishes
Both mention self hosted runner
-
v2.1.236
Runner waits for sessions to be released before shutting down
Both mention self hosted runner