Add 1.21.x releases to release notes. Update latest Compose in config

Signed-off-by: Joffrey F <joffrey@docker.com>

_config.yml

@@ -23,7 +23,7 @@ latest_stable_docker_engine_api_version: "1.37"
 docker_ce_stable_version: "18.03"
 docker_ce_edge_version: "18.05"
 docker_ee_version: "17.06"
-compose_version: "1.21.2"
+compose_version: "1.22.0"
 machine_version: "0.14.0"
 distribution_version: "2.6"
 dtr_version: "2.5"

release-notes/docker-compose.md

@@ -58,6 +58,37 @@ toc_max: 2
 - Fixed a bug that caused auth values in legacy `.dockercfg` files to be ignored
 - `docker-compose build` will no longer attempt to create image names starting with an invalid character
 
+## 1.21.2 (2018-05-03)
+
+### Bugfixes
+
+- Fixed a bug where the ip_range attirbute in IPAM configs was prevented
+  from passing validation
+
+## 1.21.1 (2018-04-27)
+
+### Bugfixes
+
+- In 1.21.0, we introduced a change to how project names are sanitized for
+  internal use in resource names. This caused issues when manipulating an
+  existing, deployed application whose name had changed as a result.
+  This release properly detects resources using "legacy" naming conventions.
+
+- Fixed an issue where specifying an in-context Dockerfile using an absolute
+  path would fail despite being valid.
+
+- Fixed a bug where IPAM option changes were incorrectly detected, preventing
+  redeployments.
+
+- Validation of v2 files now properly checks the structure of IPAM configs.
+
+- Improved support for credentials stores on Windows to include binaries using
+  extensions other than `.exe`. The list of valid extensions is determined by
+  the contents of the `PATHEXT` environment variable.
+
+- Fixed a bug where Compose would generate invalid binds containing duplicate
+  elements with some v3.2 files, triggering errors at the Engine level during
+  deployment.
 
 ## 1.21.0 (2018-04-11)