Bump gradle-docker-compose-plugin from 0.14.12 to 0.16.10

[dependabot]

Bumps gradle-docker-compose-plugin from 0.14.12 to 0.16.10.

Release notes

Sourced from gradle-docker-compose-plugin's releases.

0.16.10

Performance optimization #382

0.16.9

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

setProjectName accepts null to fallback to Docker default

No release notes provided.

setProjectName accepts null or empty value to reset to default

No release notes provided.

New Gradle Publish plugin used

No release notes provided.

MacOS-specific defaults for executable and dockerExecutable removed

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).

isRequiredBy changed in order not to break configuration avoidance

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

Custom project name propagated correctly

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.

dockerExecutor initialized before used

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

Tasks registration fixed

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).

Gradle Configuration Cache support

#351

Dots in default project name replaced

#347

Services with dashes supported correctly

#345

Docker Compose V2 support

avast/gradle-docker-compose-plugin#339 thanks @​simondwilliams

Gradle Plugin Portal publishing fixed

No release notes provided.

Commits

• e706eed feat: dc ps --services called only once (#382)
• 40349b3 chore(deps): update dependency gradle to v6.9.3
• e7e10ca fix(deps): update dependency org.yaml:snakeyaml to v1.33
• ce9f866 fix(deps): update dependency org.yaml:snakeyaml to v1.32
• 8155c72 feat: difference between states logged as info instead of lifecycle
• 9f7f19b fix(deps): update dependency org.yaml:snakeyaml to v1.31
• c15bc18 feat: setProjectName accepts null to fallback to Docker default Fixes #362
• 33cb671 feat: setProjectName accepts null or empty value as reset Fixes #362
• 9f02019 docs: Kotlin example on projectName fixed Fixes #362
• c0958f7 conf: Maven publishing fixed
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #23.