Brandon Mitchell

> It also provides some resilience if the lead maintainer disappears. I think this is a bigger challenge that should be addressed directly rather than with indirect build server requirements....

> In the case of hosting, a single-person project can choose to use a hosted system, so that they don't have to do it all themselves. I don't see why...

Hidden commands tend to be unsupported, experimental, or temporary. In this case, my plan was to remove it from `regctl` for a while since I've just used `sha256sum` instead. And...

> I understand, i agree that there are alternatives exist like you said but under bazel that means we have to fetch more binaries to have `gunzip` `shasum` and `zstdcat`...

I'd lean towards saying the `regctl digest` command isn't a core competency of `regctl`, and so I hesitate to have a dependency on it since it could be removed in...

> 1- Incrementality: doing the diffid/digest calculation as part of `regctl image mod` will yield poor results on incremental changes to the layer because it will have to redo all...

> This has something to do with the build system a little bit, what happens to the result of `regctl image mod`, if the result of previous run is thrown...

Hi @thesayyn, I'm focused on some other issues at the moment, so if you are in a rush, I'd make other plans. This is still being considered, but I haven't...

> Lots of popular registries/images are still using v1 manifests: > > ``` > $ docker pull alpine > $ docker image inspect alpine -f 'local={{.Id}} repo={{index .RepoDigests 0}}' >...

Unfortunately, since the filename is optional in that command, I'm not sure of a good way to do this that isn't a breaking change. It can also result in an...