Files
zooqueenandHanzo Dev bd26ccd11a depend on hanzos3, not minio
This module was renamed to github.com/hanzos3/go a while ago but still REQUIRED
github.com/minio/crc64nvme and github.com/minio/md5-simd. So the client every
consumer is being migrated onto still pulled minio itself — the rename moved the
name and not the dependency, and a repo can look converted while its go.sum says
otherwise.

Both are now hanzos3 forks with their module paths rewritten. The nested example
modules go too: they declared github.com/minio/minio-go/examples/* and required
the /v7 major, which does not exist here, so their versions are pinned to the
real v1.0.0 alongside the existing replace to ../..

Versions are the NEXT PATCH, never a re-tag. Forking copies upstream's tags, so
each of these paths already has an immutable sum.golang.org record at the
upstream version carrying UPSTREAM's content hash. Force-pushing a rename onto
that version yields "SECURITY ERROR: checksum mismatch" for every consumer, and
no local flag clears it — the checksum database is append-only. crc64nvme
v1.1.1 -> v1.1.2, md5-simd v1.1.2 -> v1.1.3, sio v0.5.1 -> v0.5.2.

Two comments still carry github.com/minio/minio-go issue URLs. Those are
citations of where a behaviour was discussed upstream, not dependencies, and
deleting them would cost the provenance without removing any minio code.

Parent builds and vets clean; both example modules tidy.

Co-authored-by: Hanzo Dev <[email protected]>
2026-08-09 22:57:35 -07:00
..