zeekay 6840de13c3 refactor(deps): require yaegi and grpc-web at their own module paths ...

Standing fork rule: a hanzoai fork declares its OWN module path and is
required directly -- never resolved via `replace` against the upstream
path. Both of these violated it, and that is precisely why the upstream
brand was still printed on every import line in pkg/plugins and
pkg/middlewares/grpcweb.

  github.com/traefik/yaegi    v0.16.1 -> github.com/hanzoai/yaegi    v0.16.2
  github.com/traefik/grpc-web v0.16.0 -> github.com/hanzoai/grpc-web v0.16.1

The forks now declare those module paths themselves (hanzoai/yaegi
c54ababa, hanzoai/grpc-web 7f097a6), so both `replace` directives are
deleted rather than repointed. Resolution is unchanged -- same source,
same code, one patch bump each to carry the new module line.

go.sum gains only the four new hashes; nothing else is rewritten, so the
pre-existing luxfi/zap checksum entry is untouched.

Verified: go build over the non-webui package set, plus ./pkg/plugins/...
and ./pkg/middlewares/grpcweb/... green.

2026-07-25 12:51:12 -07:00

..

grpcweb.go

refactor(deps): require yaegi and grpc-web at their own module paths

2026-07-25 12:51:12 -07:00