zeekayandHanzo Dev 59fe3fa2aa deps: reconcile luxfi/pq v1.0.3 onto the hash the tag actually resolves to ...

The v1.0.3 tag was re-pointed by a history rewrite that scrubbed a downstream
brand name from one comment line in mode.go, so the recorded zip hash no longer
matched the remote and clean-cache builds failed with a checksum SECURITY ERROR.

The new content is canonical and the difference is that single comment — no API,
no behaviour, and the module go.mod is byte-identical across both, so the
recorded /go.mod hash is unchanged. luxfi/pq v1.1.1 retracts v1.0.3 so the moved
tag stays visible instead of being laundered away here.

Co-authored-by: Hanzo Dev <[email protected]>

2026-07-28 22:51:16 -07:00

..

clob

deps: reconcile luxfi/pq v1.0.3 onto the hash the tag actually resolves to

2026-07-28 22:51:16 -07:00

harness

fix: gofmt -s across repo (CI format check)

2026-06-02 23:27:11 -07:00

scenarios

fix: gofmt -s across repo (CI format check)

2026-06-02 23:27:11 -07:00

stress

fix: gofmt -s across repo (CI format check)

2026-06-02 23:27:11 -07:00

go.mod

deps: drop poisoned luxfi/threshold v1.9.4 pin → v1.12.0

2026-07-03 15:58:59 -07:00

go.sum

deps: reconcile luxfi/pq v1.0.3 onto the hash the tag actually resolves to

2026-07-28 22:51:16 -07:00