Skip to content

Commit

Permalink
Bump 1.16.0-rc1
Browse files Browse the repository at this point in the history
Signed-off-by: Joffrey F <joffrey@docker.com>
  • Loading branch information
shin- committed Aug 18, 2017
1 parent fdbc377 commit 9bea70a
Show file tree
Hide file tree
Showing 3 changed files with 62 additions and 2 deletions.
60 changes: 60 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,66 @@
Change log
==========

1.16.0 (2017-08-31)
-------------------

### New features

#### Compose file version 3.4

- Introduced version 3.4 of the `docker-compose.yml` specification.
This version requires to be used with Docker Engine 17.06.0 or above.

#### Compose file version 2.3

- Introduced version 2.3 of the `docker-compose.yml` specification.
This version requires to be used with Docker Engine 17.06.0 or above.

- Added support for the `target` parameter in network configurations
(also available in 3.4)

- Added support for the `start_period` parameter in healthcheck
configurations

#### Compose file version 2.x

- Added support for the `blkio_config` parameter in service definitions

- Added support for setting a custom name in volume definitions using
the `name` parameter (not available for version 2.0)

#### All formats

- Added new CLI flag `--no-ansi` to suppress ANSI control characters in
output

### Bugfixes

- Fixed a bug where nested `extends` instructions weren't resolved
properly, causing "file not found" errors

- Fixed several issues with `.dockerignore` parsing

- Fixed issues where logs of TTY-enabled services were being printed
incorrectly and causing `MemoryError` exceptions

- The `$` character in the output of `docker-compose config` is now
properly escaped

- Fixed a bug where running `docker-compose top` would sometimes fail
with an uncaught exception

- Fixed a bug where `docker-compose pull` with the `--parallel` flag
would return a `0` exit code when failing

- Fixed an issue where keys in `deploy.resources` were not being validated

- Fixed an issue where the `logging` options in the output of
`docker-compose config` would be set to `null`, an invalid value

- Fixed the output of `docker-compose config` when a port definition used
`0` as the value for the published port

1.15.0 (2017-07-26)
-------------------

Expand Down
2 changes: 1 addition & 1 deletion compose/__init__.py
Original file line number Diff line number Diff line change
@@ -1,4 +1,4 @@
from __future__ import absolute_import
from __future__ import unicode_literals

__version__ = '1.16.0-dev'
__version__ = '1.16.0-rc1'
2 changes: 1 addition & 1 deletion script/run/run.sh
Original file line number Diff line number Diff line change
Expand Up @@ -15,7 +15,7 @@

set -e

VERSION="1.15.0"
VERSION="1.16.0"
IMAGE="docker/compose:$VERSION"


Expand Down

0 comments on commit 9bea70a

Please sign in to comment.