Registry Release Process

10. Compile release notes detailing features and since the last release. Update the CHANGELOG.md file.

11. Update the version file: https://github.com/docker/distribution/blob/master/version/version.go

12. Update the MAINTAINERS (if necessary), AUTHORS and .mailmap files.

13. Create a signed tag. Distribution uses semantic versioning. Tags are of the format vx.y.z[-rcn] You will need PGP installed and a PGP key. The key should be registered at keybase.io. The comment for the tag should include the release notes

14. Push the signed tag

15. Create a new release. In the case of a release candidate, tick the pre-release checkbox.

16. Update the registry binary in distribution library image repo by running the update script and opening a pull request.

17. Update the official image. Add the new version in the official images repo by appending a new version to the registry/registry file with the git hash pointed to by the signed tag. Update the major version to point to the latest version and the minor version to point to new patch release if necessary. e.g. to release 2.3.1

2.3.1 (new)

2.3.0 -> 2.3.0 (unchanged)

2 -> 2.3.1

2.3 -> 2.3.1

90. Build a new distribution/registry image on Docker hub by adding a new automated build with the new tag and re-building the images.

91. 🍰 🚑