Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update buildkite plugin docker-compose to v4 #86

Merged
merged 1 commit into from
Oct 19, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Oct 6, 2022

Mend Renovate

This PR contains the following updates:

Package Update Change
docker-compose major v3.10.0 -> v4.3.0

Release Notes

buildkite-plugins/docker-compose-buildkite-plugin

v4.3.0

Compare Source

Changes
Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v4.2.0:
+     docker-compose#v4.3.0:
        image: someimage
        workdir: /app

v4.2.0

Compare Source

Changes
Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v4.1.1:
+     docker-compose#v4.2.0:
        image: someimage
        workdir: /app

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 error
  • cache-from: will be ignored and output a warning
  • push: will be ignored and output a warning

Bug: if your pipeline uses tag-less cache-from elements, you will get a validation error that was fixed in version v4.3.0

Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v4.1.0:
+     docker-compose#v4.1.1:
        image: someimage
        workdir: /app

v4.1.0

Compare Source

Changes
Bug Fixes:
  • There was a bug where service names with periods were not being handled correctly. Fixed in (#​343) @​toote
  • Made --no-ansi apply to all commands (#​342) @​toote
Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v4.0.0:
+     docker-compose#v4.1.0:
        image: someimage
        workdir: /app

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:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v3.13.0:
+     docker-compose#v4.0.0:
        image: someimage
        workdir: /app

v3.13.0

Compare Source

Changes
Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v3.12.0:
+     docker-compose#v3.13.0:
        image: someimage
        workdir: /app

v3.12.0

Compare Source

Changes
Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v3.11.2:
+     docker-compose#v3.12.0:
        image: someimage
        workdir: /app

v3.11.2

Compare Source

Changes
Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v3.11.1:
+     docker-compose#v3.11.2:
        image: someimage
        workdir: /app

v3.11.1

Compare Source

Changes
Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v3.11.0:
+     docker-compose#v3.11.1:
        image: someimage
        workdir: /app

v3.11.0

Compare Source

Changes
Upgrading

To upgrade, update your pipeline.yml files:

steps:
  - command: test.sh
    plugins:
-     docker-compose#v3.10.0:
+     docker-compose#v3.11.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, click this checkbox.

This PR has been generated by Mend Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/docker-compose-4.x branch 4 times, most recently from ba4c9fb to 4c85537 Compare October 18, 2022 01:41
@renovate renovate bot force-pushed the renovate/docker-compose-4.x branch from 4c85537 to 77fb576 Compare October 19, 2022 03:17
@toote toote merged commit 0d0b555 into master Oct 19, 2022
@toote toote deleted the renovate/docker-compose-4.x branch October 19, 2022 03:19
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.

1 participant