v0.0.8 rules_docker fixes

This release contains various fixes for issues uncovered by users of bazelbuild/rules_docker.

v0.0.7: Flexible docker_name

This allows users of docker_name to relax some of its strict requirements around specifying fully-qualified tag, digest, repository.

v0.0.6: Support pushing to yet more registries

This release switches us to using POST/PATCH/PUT uploads, which work with Bintray.

v0.0.5: Support pushing to more registries

This release changes the method used for uploading layer blobs to the POST/PUT method because the monolithic POST method isn't widely supported.

v0.0.4: Optimizations for docker_build

This release contains numerous optimizations for dealing with images whose underlying representation is uncompressed (e.g. FromTarball). This is mostly for scenarios where those layers are destined to be stored uncompressed (e.g. save.py).

The primary scenario it targets is Bazel docker_build which significantly regressed going through our compressed abstractions, but with this release and some forthcoming changes it should be comparable to the version bundled with Bazel previously.

v0.0.3: Supporting Bazel's docker_build

This release contains all of the supporting changes needed to migrate Bazel's docker_build to use this library for it's metadata and tarball manipulations (in addition to relying on this for pusher/puller).

v0.0.2

Adds a dependency on "six" to fix problems running the released PAR files in some environments.

v0.0.1

Initial release of the google/containerregistry client library.

v0.0.0-test

Initial test release of google/containerregistry to verify that the binary release triggers are WAI.