deps: zap-proto/http v0.1.0 has no Dial, so put v0.3.1 back

`go build ./...` has been failing on main with

    pkg/server/service/zap_backend.go:176: undefined: zaphttp.Dial

since the acme single-writer commit, which rewrote go.mod wholesale and took
zap-proto/http back from v0.3.1 to v0.1.0 along with go 1.26.5 -> 1.26.4, zip,
the aws sdk and a dozen others. Dial arrived after v0.1.0, and zap_backend.go
is the one caller. This restores that single line; the rest of that rewrite is
left alone, since only this one stops the tree compiling.

Verified against a clean checkout of main: the same package fails there and
builds with the version restored.
This commit is contained in:
2026-08-10 13:00:46 -07:00
parent 2a40ec664c
commit b0a4521c50
2 changed files with 3 additions and 1 deletions
+1 -1
View File
@@ -108,7 +108,7 @@ require (
github.com/luxfi/trace v1.4.0
github.com/luxfi/zap v1.2.6
github.com/prometheus/client_golang v1.23.2
github.com/zap-proto/http v0.1.0
github.com/zap-proto/http v0.3.1
)
require (
+2
View File
@@ -1360,6 +1360,8 @@ github.com/zap-proto/go v1.3.0 h1:S3rMoawwhH/BbSZ4G8zG05hJoQnMSMDPzIq75diCTqE=
github.com/zap-proto/go v1.3.0/go.mod h1:914SNGTH6Rv3Yu1MweWJBPEN8FZlo5C39QyhaB0C7Q0=
github.com/zap-proto/http v0.1.0 h1:aA8NmU/a0yM7QFU5tjXPYHFiBUcoHn92wjMy181o50M=
github.com/zap-proto/http v0.1.0/go.mod h1:UYfGhDDCetgxs65XSev8Lpf65COg5vKQK+cWwZGh4zQ=
github.com/zap-proto/http v0.3.1 h1:A2rCPWYCX866eAsdiWuns0dvWnBmViZtGm4pwX7jwlY=
github.com/zap-proto/http v0.3.1/go.mod h1:UYfGhDDCetgxs65XSev8Lpf65COg5vKQK+cWwZGh4zQ=
github.com/zap-proto/zip v1.1.0 h1:JDIVblpbbutKHt+wzVr4VACyJZwytGuR1aMuyQqOhnw=
github.com/zap-proto/zip v1.1.0/go.mod h1:8ENateaAvSg2ACuO4B03ntl8dGeWxnpXpOc9zRDhZPA=
github.com/zeebo/xxh3 v1.0.2 h1:xZmwmqxHZA8AI603jOQ0tMqmBr9lPeFwGg6d+xy9DC0=