v0.9.3

What's Changed

• Allow to use trust-dns by @astoycos in #43
• cleanups by @flavio in #44
• Bump actions/checkout from 2.3.4 to 3.0.2 by @dependabot in #45
• Release v0.9.3 by @flavio in #46

New Contributors

• @astoycos made their first contribution in #43

Full Changelog: v0.9.2...v0.9.3

oci-distribution v0.9.2

Changes since v0.9.1:

• fix: Fix workaround used when pushing to ECR

oci-distribution 0.9.1

Changes since v0.9.0:

• Fix: ensure layers bigger than 4Mb can be pushed (issue #35)

oci-distribution v0.9.0

Changes since 0.8.1:

• Add support for manifest list and image index manifest types
• Fix: address Windows incompatibility issues
• [API breaking] Change the API of Client::push: return also the manifest digest
• Fix: do not fail when an OCI manifest is returned. The library can handle them too
• Fix: Be explicit about the traits supported by the platform resolver function. This is needed to use the Client behind a dynamic reference.
• [API breaking] Fix: pushing of images with multiple layers now works
• Enhancement: ensure the manifest pushed are using canonicalized JSON
• Enhancement: improve test suite by performing certain operations against a real container registry
• Enhancement: export the pull_layer and the auth APIs
• Enhancement: support of pushing manifest lists
• [API breaking] Enhancement: get rid of anyhow::Result, instead provide specific error types defined inside of the library
• Enhancement: workaround AWS ECR issues. The registry is not compliant with the OCI distribution specification. Work around these issues
  instead of refusing to work with this type of registries.
• [API breaking] fix/enhancement: better handling of OCI image annotations

oci-distribution v0.8.1

This is a patch release that contains the following fixes:

• ClientConfig: define accept_invalid_hostnames attribute only when native-tls is being used
• Improve parsing of container image names: this ensure Reference behaves in the same way as native Go libraries do when parsing oci names
• Fix interactions with GitHub Container Registry: ensure anonymous operations (like pull) can be performed

The following cleanups have been done:

• Remove Cargo.lock file from repository
• Remove the in-tree version of the www-authenticate crate: use the latest official release of it, which contains all the changes and fixes oci-distribution did.
• Fix all clippy warnings
• Fix cargo deny execution