{"push_id":560398431,"size":1,"distinct_size":1,"ref":"refs/heads/push-all-tags","head":"1717afe70c9bb90b2adfe34e5183292cb2e6a4ea","before":"983ea4b91081e2052ada8e96d8f9eaa94811107e","commits":[{"sha":"1717afe70c9bb90b2adfe34e5183292cb2e6a4ea","author":{"email":"63efd86fa22882ae89b6027b22a36e4db1f4214d@docker.com","name":"Stephen J Day"},"message":"Push all tags when no tag is specified\n\nIn Docker 1.4, a push with no tag specified resulted in pushing all the tags\nfor an image. With changes in 1.5, this behavior was broken. The issue was the\ninteraction between the engine and the client. When requesting the manifest, if\nthe tag was not specified, the engine defaulted to latest. In cases where\nlatest was defined, only latest would be pushed. If latest was not defined, the\npush would fail with an error message.  This behavior was the same between v1\nand v2 pushes.\n\nWe address this by sending all the manifests for all tagged images if the tag\nis not specified when fetching the manifest. The engine command image_manifest\nwas modified to return a collection of manifests rather than just a single one\nto support this. The client code then loops to push each manifest individually.\n\nSigned-off-by: Stephen J Day <stephen.day@docker.com>","distinct":true,"url":"https://api.github.com/repos/stevvooe/docker/commits/1717afe70c9bb90b2adfe34e5183292cb2e6a4ea"}]}