{"push_id":756454527,"size":3,"distinct_size":3,"ref":"refs/heads/master","head":"44c7fb9e6e7e58e88d38d93b5f1f6da6a54d28ff","before":"fee9a9a469867f252d63adff901f9af1aa77bcd2","commits":[{"sha":"d00586de9f21e6e7d3736646b2f434e76a25f00a","author":{"email":"63efd86fa22882ae89b6027b22a36e4db1f4214d@docker.com","name":"Stephen J Day"},"message":"Use correct path for manifest revision path\n\nUnfortunately, the refactor used the incorrect path for manifest links within a\nrepository. While this didn't stop the registry from working, it did break\ncompatibility with 2.0 deployments for manifest fetches.\n\nTests were added to ensure these are locked down to the appropriate paths.\n\nSigned-off-by: Stephen J Day <stephen.day@docker.com>","distinct":true,"url":"https://api.github.com/repos/docker/distribution/commits/d00586de9f21e6e7d3736646b2f434e76a25f00a"},{"sha":"06a098c632aee74619a06f88c23a06140f442a6f","author":{"email":"63efd86fa22882ae89b6027b22a36e4db1f4214d@docker.com","name":"Stephen J Day"},"message":"Maintain manifest link compatibility\n\nUnfortunately, the 2.1 releease has written manfiest links into the wrong\ndirectory. This doesn't affect new 2.1 deployments but fixing this to be 2.0\nbackwards compatible has broken 2.1.0 compatibility. To ensure we have\ncompatibility between 2.0, 2.1.0 and future releases, we now check one of\nseveral locations to identify a manifest link.\n\nSigned-off-by: Stephen J Day <stephen.day@docker.com>","distinct":true,"url":"https://api.github.com/repos/docker/distribution/commits/06a098c632aee74619a06f88c23a06140f442a6f"},{"sha":"44c7fb9e6e7e58e88d38d93b5f1f6da6a54d28ff","author":{"email":"0a635b283566a554fd91555c968d9ef98402b500@docker.com","name":"Richard Scothern"},"message":"Merge pull request #864 from stevvooe/use-correct-manifest-link\n\nregistry/storage: use correct manifest link","distinct":true,"url":"https://api.github.com/repos/docker/distribution/commits/44c7fb9e6e7e58e88d38d93b5f1f6da6a54d28ff"}]}