Skip to content

Conversation

@shin-
Copy link

@shin- shin- commented Jun 21, 2018

Automated release for docker-compose 1.22.0-rc1

Features

Compose format version 3.7

  • Introduced version 3.7 of the docker-compose.yml specification.
    This version requires Docker Engine 18.06.0 or above.

  • Added support for rollback_config in the deploy configuration

  • Added support for the init parameter in service configurations

  • Added support for extension fields in service, network, volume, secret,
    and config configurations

Compose format version 2.4

  • Added support for extension fields in service, network,
    and volume configurations

Bugfixes

  • Fixed a bug that prevented deployment with some Compose files when
    DOCKER_DEFAULT_PLATFORM was set

  • Compose will no longer try to create containers or volumes with
    invalid starting characters

  • Fixed several bugs that prevented Compose commands from working properly
    with containers created with an older version of Compose

  • Fixed an issue with the output of docker-compose config with the
    --compatibility-mode flag enabled when the source file contains
    attachable networks

  • Fixed a bug that prevented the gcloud credential store from working
    properly when used with the Compose binary on UNIX

  • Fixed a bug that caused connection errors when trying to operate
    over a non-HTTPS TCP connection on Windows

  • Fixed a bug that caused builds to fail on Windows if the Dockerfile
    was located in a subdirectory of the build context

  • Fixed an issue that prevented proper parsing of UTF-8 BOM encoded
    Compose files on Windows

shin- and others added 30 commits March 30, 2018 18:02
Fix port serialization with external IP
Make sure error messages are unicode strings before combining
- add support for `docker-compose exec --workdir|-w`
- add support for `docker-compose build --compress`
- add support for `docker-compose pull --no-parallel`, drop deprecated
  option `--parallel`

Signed-off-by: Harald Albers <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Add support for features added in 1.21.0 to bash completion
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
vdemeester and others added 14 commits May 30, 2018 13:36
Ignoring it on docker-compose

Signed-off-by: Vincent Demeester <[email protected]>
Add 3.7 schema and add rollback_config to it
As for top-level key, any 3rd-level key which starts with `x-` will be
ignored by compose. This allows for users to:
* include additional metadata in their compose files
* create YAML anchor objects that can be re-used in other parts of the config

This matches a similar feature in the swagger spec definition:
https://swagger.io/specification/#specificationExtensions

This means a composefile like the following is valid

```
verison: "3.7"
services:
  foo:
    image: foo/bar
    x-foo: bar
network:
  bar:
    x-bar: baz
```

It concerns services, volumes, networks, configs and secrets.

Signed-off-by: Vincent Demeester <[email protected]>
Allow `x-*` extension on 3rd level objects
> Run an init inside the container that forwards signals and reaps
> processes

This is already supported in 2.4 schema

Signed-off-by: Vincent Demeester <[email protected]>
Add `init` support in 3.7 schema
Signed-off-by: Joffrey F <[email protected]>
Use original LD_LIBRARY_PATH when shelling out to credential stores
Better support for UTF8+bom Compose files
Signed-off-by: Joffrey F <[email protected]>
shin- added 2 commits June 21, 2018 13:28
Signed-off-by: Joffrey F <[email protected]>
Signed-off-by: Joffrey F <[email protected]>
@shin- shin- force-pushed the bump-1.22.0-rc1 branch from c27de1b to 1fb5039 Compare June 21, 2018 20:28
@GordonTheTurtle
Copy link

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:

$ git clone -b "bump-1.22.0-rc1" [email protected]:docker/compose.git somewhere
$ cd somewhere
$ git rebase -i HEAD~842354177128
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

Signed-off-by: Joffrey F <[email protected]>
@shin- shin- closed this Jun 21, 2018
@shin- shin- reopened this Jun 21, 2018
@shin- shin- merged commit bdd7d47 into release Jun 21, 2018
@shin- shin- deleted the bump-1.22.0-rc1 branch June 27, 2018 22:09
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants