mirror of
https://github.com/agent-substrate/substrate.git
synced 2026-10-16 05:49:56 +08:00
Dmitry Berkovich
228fde4949
## Summary Bumps `github.com/google/go-containerregistry` v0.21.5 → v0.21.7. Phase 0 of #463. v0.21.6 fixed the memory spike in `mutate.Extract` described in #120 (upstream fix: google/go-containerregistry#2190, merged as google/go-containerregistry@38d6e4087c): extraction is now refactored into a per-layer `extractLayer` function, so each layer's decompressor and HTTP response body are closed as soon as that layer is processed, instead of all being held open via deferred `Close` calls until the entire (multi-GB) extraction completes. atelet's pull path goes through `memorypullcache.Fetch` → `mutate.Extract`, so this directly caps its extract-time memory. Note this is only interim relief: #437's unbounded cache retention is untouched and is addressed by the redesign in #463. ## Changes - `go-containerregistry` v0.21.5 → v0.21.7, plus required transitive bumps: `docker/cli`, `klauspost/compress`, `golang.org/x/sync`, `golang.org/x/sys` - `go mod tidy` + `go mod vendor`; the `containerd/stargz-snapshotter/estargz` vendor tree drops out (upstream removed the estargz integration; nothing in substrate used it), along with `vbatts/tar-split` and `mitchellh/go-homedir` ## Testing - `go build ./...` passes - Full `go test ./...` passes - Verified the layer-close fix is present in the vendored `pkg/v1/mutate/mutate.go` Fixes #120 🤖 Generated with [Claude Code](https://claude.com/claude-code)