Releases: palantir/docker-compose-rule
Releases · palantir/docker-compose-rule
2.3.0
Type |
Description |
Link |
Fix |
Use Docker Compose v2 by default when constructing a DockerComposeExecutable explicitly. |
#744 |
2.2.0
Type |
Description |
Link |
Improvement |
Project names are no longer validation. Any value can be used for a project name. |
#741 |
2.1.0
Type |
Description |
Link |
Improvement |
Include lastException as cause when docker-compose up fails |
#732 |
2.0.0
Type |
Description |
Link |
Break |
Enable docker-compose v2 by default |
#729 |
1.9.0
Type |
Description |
Link |
Feature |
docker-compose-rule now adds (opt in) support for docker-compose v2 |
#722 |
1.8.0
Type |
Description |
Link |
Fix |
Map port range mappings from docker ps output. |
#695 |
1.7.0
Type |
Description |
Link |
Fix |
Use newer version of conjure-java-runtime that exists on maven central. |
#618 |
1.6.0
Automated release, no documented user facing changes
1.5.0
Type |
Description |
Link |
Improvement |
Add option to omit the project name |
#495 |
1.4.2
Type |
Description |
Link |
Fix |
Fix parsing of docker-compose output
Set the COLUMNS environment variable to an artificially large value for the docker-compose process. This works around newer versions of docker-compose (at least 1.25.0-rc4+) which adjust their output based on the width of the terminal. |
#424 |