fix(deps): update dependency com.avast.gradle:gradle-docker-compose-plugin to v0.17.6

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
com.avast.gradle:gradle-docker-compose-plugin	0.15.2 -> 0.17.6

---

Release Notes

avast/gradle-docker-compose-plugin (com.avast.gradle:gradle-docker-compose-plugin)

v0.17.6

Compare Source

Deprecation for Gradle 9.0 handled - task must register usage of a build service using Task.usesService method.

#​432

v0.17.5

Compare Source

Docker Compose 2.21.0 introduced a breaking change in docker compose ps output format, this release adds support for the new format (while supporting also the old format).

v0.17.4

Compare Source

Ensure the -f parameters go right after docker compose.

v0.17.3

Compare Source

Revert of a change introduced in 0.17.0 that introduced stderr reading when executing docker command. It leads to an unexpected output if Docker is not fully correctly installed and prints warnings to stderr (while stdout is valid).

v0.17.2

Compare Source

Safer JSON parsing of docker compose ps output.

v0.17.1

Compare Source

Update to Gradle v8.

v0.17.0

Compare Source

• Migrated to the latest Gradle 7.x
• As Docker Compose V1 is deprecated, default value of useDockerComposeV2 property was changed from false to true, so docker compose is used by default (instead of docker-compose).
• More version formats handled in the VersionNumber.parse method.
• Durations stripped from cache key.

v0.16.13: useDockerComposeV2 introduced

Compare Source

v0.16.12: Gradle 8 compatibility

Compare Source

Usage of deprecated internal VersionNumber class removed #​399

v0.16.11

Compare Source

Project name lowercased #​386

v0.16.10

Compare Source

Performance optimization #​382

v0.16.9

Compare Source

The level of a log message changed from lifecycle to info.

v0.16.8: setProjectName accepts null to fallback to Docker default

Compare Source

v0.16.7: setProjectName accepts null or empty value to reset to default

Compare Source

v0.16.6: New Gradle Publish plugin used

Compare Source

v0.16.5: MacOS-specific defaults for executable and dockerExecutable removed

Compare Source

The defaults used to be /usr/local/bin/docker-compose and /usr/local/bin/docker, now it is just plain docker-compose and docker (for all platforms).

v0.16.4: isRequiredBy changed in order not to break configuration avoidance

Compare Source

This release changes the behavior of isRequiredBy so the Up tasks should be executed as the last dependency of the configured task. Till now, we have this optimization for classes tasks only.

As reported in #​352

v0.16.3: Custom project name propagated correctly

Compare Source

projectName property wasn't properly used due to a bug introduced in 0.16.0.

The problem was that the property was declared as a plain String instead of Provider<String>, so a change to the original value wasn't propagated to ComposeExecutor.

v0.16.2: dockerExecutor initialized before used

Compare Source

As reported, it could happen that dockerExecutor was used before it was initialized. This release fixes this potential issue.

v0.16.1: Tasks registration fixed

Compare Source

It is possible to get A dependency must not be empty error with 0.16.0 version of the plugin. This release should solve this issue (reported here).

v0.16.0: Gradle Configuration Cache support

Compare Source

#​351

---

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.