go-git/v6 alpha.5 to beta.1 changes HTTP credential scoping and redirects, introduces CredentialsDroppedError, and removes dumb HTTP transport support. Archie uses go-git for authenticated clone/fetch/push and installs transport handling in internal/worktree/worktree.go. Investigate those actual callers against beta.1; adapt only where the new API or behavior requires it. Keep git execution in the daemon and credentials out of agent containers.
Acceptance criteria
Supported authenticated clone/fetch/push work under beta.1; same-origin and cross-origin redirects obey credential boundaries; dropped credentials and unsupported dumb HTTP endpoints produce actionable redacted errors; no token leaks or compensating transport fallback; security regression tests where behavior changes and task check pass.
Notes
Audit completed in be31522e with no production migration required. Manager.auth already uses gitclient.WithHTTPAuth, whose beta.1 contract scopes credentials to the repository origin. Existing wrapped errors preserve CredentialsDroppedError and upstream actionable dumb-HTTP errors without exposing tokens. TestForgeHTTPAuthentication exercises the actual Manager against git http-backend: authenticated clone, commit, push, and resume/fetch; same-origin redirects work; cross-origin credentials are withheld and refusal is diagnostic; dumb HTTP is explicitly rejected. Final task check and race test passed.
Imported from beads archie-core-2rjq · GitHub #1545 · type task · priority P2 · created 2026-10-09
go-git/v6 alpha.5 to beta.1 changes HTTP credential scoping and redirects, introduces CredentialsDroppedError, and removes dumb HTTP transport support. Archie uses go-git for authenticated clone/fetch/push and installs transport handling in internal/worktree/worktree.go. Investigate those actual callers against beta.1; adapt only where the new API or behavior requires it. Keep git execution in the daemon and credentials out of agent containers.
### Acceptance criteria
Supported authenticated clone/fetch/push work under beta.1; same-origin and cross-origin redirects obey credential boundaries; dropped credentials and unsupported dumb HTTP endpoints produce actionable redacted errors; no token leaks or compensating transport fallback; security regression tests where behavior changes and task check pass.
### Notes
Audit completed in be31522e with no production migration required. Manager.auth already uses gitclient.WithHTTPAuth, whose beta.1 contract scopes credentials to the repository origin. Existing wrapped errors preserve CredentialsDroppedError and upstream actionable dumb-HTTP errors without exposing tokens. TestForgeHTTPAuthentication exercises the actual Manager against git http-backend: authenticated clone, commit, push, and resume/fetch; same-origin redirects work; cross-origin credentials are withheld and refusal is diagnostic; dumb HTTP is explicitly rejected. Final task check and race test passed.
---
_Imported from beads `archie-core-2rjq` · GitHub #1545 · type task · priority P2 · created 2026-10-09_
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
go-git/v6 alpha.5 to beta.1 changes HTTP credential scoping and redirects, introduces CredentialsDroppedError, and removes dumb HTTP transport support. Archie uses go-git for authenticated clone/fetch/push and installs transport handling in internal/worktree/worktree.go. Investigate those actual callers against beta.1; adapt only where the new API or behavior requires it. Keep git execution in the daemon and credentials out of agent containers.
Acceptance criteria
Supported authenticated clone/fetch/push work under beta.1; same-origin and cross-origin redirects obey credential boundaries; dropped credentials and unsupported dumb HTTP endpoints produce actionable redacted errors; no token leaks or compensating transport fallback; security regression tests where behavior changes and task check pass.
Notes
Audit completed in
be31522ewith no production migration required. Manager.auth already uses gitclient.WithHTTPAuth, whose beta.1 contract scopes credentials to the repository origin. Existing wrapped errors preserve CredentialsDroppedError and upstream actionable dumb-HTTP errors without exposing tokens. TestForgeHTTPAuthentication exercises the actual Manager against git http-backend: authenticated clone, commit, push, and resume/fetch; same-origin redirects work; cross-origin credentials are withheld and refusal is diagnostic; dumb HTTP is explicitly rejected. Final task check and race test passed.Imported from beads
archie-core-2rjq· GitHub #1545 · type task · priority P2 · created 2026-10-09