Files
zeekayandHanzo Dev 97e5b7368d chore(cache): delete the redis cache backend — drops gomodule/redigo
client/cache/redis was a second, foreign Redis client living alongside
our own. Our KV client is github.com/hanzokv/go; the session backends
were already moved onto it (kv, kv_cluster, kv_sentinel). redigo was
the last thing keeping a competing driver in the tree — one way, not
two.

Proof it is dead:
  - Zero imports of github.com/hanzoai/beego/v2/client/cache/redis
    anywhere. The only two textual hits in the whole workspace are
    commented-out doc examples inside the backend's own file
    (client/cache/redis/redis.go:24) and its memcache sibling.
  - There is no adapter/ tree in this fork, so no v1-compat shim
    re-exports it.
  - The backend is reachable only via a blank import (it self-registers
    in init() -> cache.Register). No blank import of it exists.
  - Workspace-wide: only cloud, cloud-godview and cloud-oss48 import
    hanzoai/beego at all, and all three import server/web only.
    Six other repos carry it as an // indirect go.mod entry with no
    Go source import.

Dependency that falls out:
  github.com/gomodule/redigo — used only by the deleted files. Dropped
  the require AND the `replace ... => v1.8.8` pin. `go mod why` now
  reports "main module does not need" it and `go list -deps ./...`
  resolves zero redigo packages, i.e. it compiles into nothing. One
  /go.mod-only hash line survives in go.sum because ledisdb's own
  go.mod requires it; that is graph metadata, not compiled code.

Deliberately kept:
  - CI service `redis:latest` on 6379 in .github/workflows/test.yml —
    still required by server/web/session/{kv,kv_cluster,kv_sentinel},
    which run hanzokv/go against a redis-compatible server.
  - client/cache/memcache and client/cache/ssdb. Both are equally
    unreferenced, but deleting them drops no dependency: their clients
    (bradfitz/gomemcache, ssdb/gossdb) are also used by the live
    server/web/session/{memcache,ssdb} providers.

Verified: `CGO_ENABLED=0 GOWORK=off GOFLAGS=-mod=mod go build ./...`
produces the identical pre-existing core/logs/alils lz4 failure before
and after and nothing new; `go build ./client/... ./server/...` exit 0;
`go test ./client/cache/` ok.

Co-authored-by: Hanzo Dev <[email protected]>
2026-07-26 10:33:39 -07:00
..