chore(deps): update buildkite plugin docker-compose to v4 #86
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v3.10.0
->v4.3.0
Release Notes
buildkite-plugins/docker-compose-buildkite-plugin
v4.3.0
Compare Source
Changes
cache-from
(#350) @tootessh
support (#347) @tooteUpgrading
To upgrade, update your
pipeline.yml
files:v4.2.0
Compare Source
Changes
target
option (#346) @tooteUpgrading
To upgrade, update your
pipeline.yml
files:v4.1.1
Compare Source
Bugfixes
Invalid tags in some options caused errors with docker-compose calls. That behaviour changes so that invalid tag values in:
build
: will cause a more descriptive errorcache-from
: will be ignored and output a warningpush
: will be ignored and output a warningBug: if your pipeline uses tag-less
cache-from
elements, you will get a validation error that was fixed in version v4.3.0Upgrading
To upgrade, update your
pipeline.yml
files:v4.1.0
Compare Source
Changes
Bug Fixes:
--no-ansi
apply to all commands (#342) @tooteUpgrading
To upgrade, update your
pipeline.yml
files:v4.0.0
Compare Source
Changes
This is a major release because it changes the default behaviour when a compose file has no version. We are being cautious as it is impossible to test all scenarios, but it is likely you can just upgrade, and nothing will break unless you are using a very old docker-compose version (before v1.27.0).
Dependency Updates
Upgrading
To upgrade, update your
pipeline.yml
files:v3.13.0
Compare Source
Changes
Upgrading
To upgrade, update your
pipeline.yml
files:v3.12.0
Compare Source
Changes
Upgrading
To upgrade, update your
pipeline.yml
files:v3.11.2
Compare Source
Changes
version
keys in docker-compose config (#336) @orien @tooteUpgrading
To upgrade, update your
pipeline.yml
files:v3.11.1
Compare Source
Changes
Upgrading
To upgrade, update your
pipeline.yml
files:v3.11.0
Compare Source
Changes
Upgrading
To upgrade, update your
pipeline.yml
files: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.