v0.8

• Add support for registries with self-signed certs - dc3df03

v0.7

• Support --version flag - a28ed69

v0.6

• Reinstate Client interface - 1b2ef82
• Refactoring - a82a43d
• Improve test coverage - 9bb5077
• Support pushing a manifest list from a layout - 8acb4ca

Refactoring notes

I noticed that the LayoutPath interface is in the wrong package since it is ggcr-specific and the registry package is intended to be general purpose. Similarly for the AppendToLayout method of the Image interface.

I tried moving these into the ggcr package, but ended up not being able to generate the existing mocks because of limitations in counterfeiter and/or golang in the use of interfaces. Counterfeiter failed thus:

go list repeated package github.com/pivotal/image-relocation/pkg/registry/ggcr [github.com/pivotal/image-relocation/pkg/registry/ggcr.test] with different values

I also tried moving the LayoutPath interface along with most of layout.go into a path package, but ended up with a package import cycle between ggcr and path.

So I settled for placing LayoutPath in its own package, which at least gets it out of the registry package.

I had to use a type assertion to enable me to move the AppendToLayout method to the ggcr package. Without a type assertion, I ended up with interfaces that either wouldn't compile or which caused counterfeiter to fail.

v0.5

• Set up release action - 28a4e87
• Re-instate ability for layout add to use an existing layout - 6e410f4
• Preserve tag when writing to a tagged and digested image reference - 146bd40

v0.4

• Support copying image indexes - @glyn
• Use gren for releasing - @glyn

v0.3

• [closed] Mention some alternatives #24
• [closed] layout add should use existing layout if there is one #26
• [closed] Provide more context #22
• [closed] Revert reading images from the docker daemon #21
• [closed] bump docker #19
• [closed] Try docker daemon before reading remote image #18

v0.2: Try docker daemon before reading remote image

See https://github.com/deislabs/duffle/issues/828#issuecomment-519013774.

Bump the go-containerregistry dependency and use a corresponding version of
docker.

Handle an empty image name more gracefully (than panicking).

Initial release

v0.1

Fix typo