buildkite-plugins/docker-compose-buildkite-plugin (docker-compose)
### [`v5.0.0`](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/releases/tag/v5.0.0): (ππ» We Did It!)
[Compare Source](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/compare/v4.16.0...v5.0.0)
#### Changes - Major Release β οΈ
Based on the discussion from [#390](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/390), we are officially making docker compose v2 the default one of this plugin, and added other backward incompatible changes:
- Removing double build commands from docker-compose plugin in run/push and unify the corresponding parameters instead - see [discussion](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/309#issuecomment-1440826854) ([#416](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/416)) [@toote](https://togithub.com/toote)
- Defaults TTY to false to reduce log amount and changes log collapsing to apply to all commands (not just run) ([#417](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/417)) [@toote](https://togithub.com/toote)
- Simplify configuration removing image-repository and image-name configurations, and change the way build and push interact and corrects `--target` option ([#418](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/418)) [@toote](https://togithub.com/toote)
- Reduced the complexity of the cache-from option. Now it is just a pass-through to the corresponding options in docker compose ([#419](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/419)) [@toote](https://togithub.com/toote)
- Make CLI v2 as default ([#420](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/420)) [@toote](https://togithub.com/toote)
- Documentation updates ([#421](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/421)) [@toote](https://togithub.com/toote)
#### Notes
Thanks to everyone who provided their input and feedback and to [@tomowatt](https://togithub.com/tomowatt) for conducting an incredibly thorough and detailed review π
#### Upgrading
Check our [notes](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/blob/master/docs/upgrading-to-v5.md) for more detailed information on this major release that should help you review and provide you with actionable steps for you to upgrade.
To upgrade, update your `pipeline.yml` files:
```diff
steps:
- command: test.sh
plugins:
- docker-compose#v4.16.0:
+ docker-compose#v5.0.0:
image: someimage
workdir: /app
```
Configuration
π Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.
This PR contains the following updates:
v4.16.0
->v5.0.0
Release Notes
buildkite-plugins/docker-compose-buildkite-plugin (docker-compose)
### [`v5.0.0`](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/releases/tag/v5.0.0): (ππ» We Did It!) [Compare Source](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/compare/v4.16.0...v5.0.0) #### Changes - Major Release β οΈ Based on the discussion from [#390](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/390), we are officially making docker compose v2 the default one of this plugin, and added other backward incompatible changes: - Removing double build commands from docker-compose plugin in run/push and unify the corresponding parameters instead - see [discussion](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/309#issuecomment-1440826854) ([#416](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/416)) [@toote](https://togithub.com/toote) - Defaults TTY to false to reduce log amount and changes log collapsing to apply to all commands (not just run) ([#417](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/417)) [@toote](https://togithub.com/toote) - Simplify configuration removing image-repository and image-name configurations, and change the way build and push interact and corrects `--target` option ([#418](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/418)) [@toote](https://togithub.com/toote) - Reduced the complexity of the cache-from option. Now it is just a pass-through to the corresponding options in docker compose ([#419](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/419)) [@toote](https://togithub.com/toote) - Make CLI v2 as default ([#420](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/420)) [@toote](https://togithub.com/toote) - Documentation updates ([#421](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/issues/421)) [@toote](https://togithub.com/toote) #### Notes Thanks to everyone who provided their input and feedback and to [@tomowatt](https://togithub.com/tomowatt) for conducting an incredibly thorough and detailed review π #### Upgrading Check our [notes](https://togithub.com/buildkite-plugins/docker-compose-buildkite-plugin/blob/master/docs/upgrading-to-v5.md) for more detailed information on this major release that should help you review and provide you with actionable steps for you to upgrade. To upgrade, update your `pipeline.yml` files: ```diff steps: - command: test.sh plugins: - docker-compose#v4.16.0: + docker-compose#v5.0.0: image: someimage workdir: /app ```Configuration
π Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
π¦ Automerge: Disabled by config. Please merge this manually once you are satisfied.
β» Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
π Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.