dependabot[bot] opened a new pull request, #23688: URL: https://github.com/apache/beam/pull/23688
Bumps [gradle-docker-compose-plugin](https://github.com/avast/gradle-docker-compose-plugin) from 0.14.12 to 0.16.9. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/avast/gradle-docker-compose-plugin/releases";>gradle-docker-compose-plugin's releases</a>.</em></p> <blockquote> <h2>0.16.9</h2> <p>The level of a log message changed from lifecycle to info.</p> <h2>setProjectName accepts null to fallback to Docker default</h2> <p>No release notes provided.</p> <h2>setProjectName accepts null or empty value to reset to default</h2> <p>No release notes provided.</p> <h2>New Gradle Publish plugin used</h2> <p>No release notes provided.</p> <h2>MacOS-specific defaults for executable and dockerExecutable removed</h2> <p>The defaults used to be <code>/usr/local/bin/docker-compose</code> and <code>/usr/local/bin/docker</code>, now it is just plain <code>docker-compose</code> and <code>docker</code> (for all platforms).</p> <h2>isRequiredBy changed in order not to break configuration avoidance</h2> <p>This release changes the behavior of <code>isRequiredBy</code> so the <code>Up</code> tasks should be executed as the last dependency of the configured task. Till now, we have this optimization for <code>classes</code> tasks only.</p> <p>As reported in <a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/issues/352";>#352</a></p> <h2>Custom project name propagated correctly</h2> <p><code>projectName</code> property wasn't properly used due to a bug introduced in <code>0.16.0</code>.</p> <blockquote> <p>The problem was that the property was declared as a plain <code>String</code> instead of <code>Provider<String></code>, so a change to the original value wasn't propagated to <code>ComposeExecutor</code>.</p> </blockquote> <h2>dockerExecutor initialized before used</h2> <p>As <a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/pull/351#issuecomment-1114815875";>reported</a>, it could happen that <code>dockerExecutor</code> was used before it was initialized. This release fixes this potential issue.</p> <h2>Tasks registration fixed</h2> <p>It is possible to get <code>A dependency must not be empty</code> error with <code>0.16.0</code> version of the plugin. This release should solve this issue (reported <a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/pull/351#issuecomment-1114623955";>here</a>).</p> <h2>Gradle Configuration Cache support</h2> <p><a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/issues/351";>#351</a></p> <h2>Dots in default project name replaced</h2> <p><a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/issues/347";>#347</a></p> <h2>Services with dashes supported correctly</h2> <p><a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/issues/345";>#345</a></p> <h2>Docker Compose V2 support</h2> <p><a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/pull/339";>avast/gradle-docker-compose-plugin#339</a> thanks <a href="https://github.com/simondwilliams";><code>@​simondwilliams</code></a></p> <h2>Gradle Plugin Portal publishing fixed</h2> <p>No release notes provided.</p> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/8155c72073039e293b9bd43cfbe6e6f068a31662";><code>8155c72</code></a> feat: difference between states logged as info instead of lifecycle</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/9f7f19b426d9ee6a0acba6e485f4f83a215d3545";><code>9f7f19b</code></a> fix(deps): update dependency org.yaml:snakeyaml to v1.31</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/c15bc180a5fbaa3aacac7643f50016dec4127e4d";><code>c15bc18</code></a> feat: setProjectName accepts null to fallback to Docker default Fixes <a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/issues/362";>#362</a></li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/33cb6711f485b11fee3879dbeaf8c0a6a9ff2fba";><code>33cb671</code></a> feat: setProjectName accepts null or empty value as reset Fixes <a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/issues/362";>#362</a></li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/9f0201937e0f1d8e378c9b14d101a351b632ce64";><code>9f02019</code></a> docs: Kotlin example on projectName fixed Fixes <a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/issues/362";>#362</a></li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/c0958f74ed4ac82262cb890830417d2f356fb9fd";><code>c0958f7</code></a> conf: Maven publishing fixed</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/4a013c0c17190d547e347a7f865c1c21f0ac7707";><code>4a013c0</code></a> chore(deps): update plugin com.gradle.plugin-publish to v1 (<a href="https://github-redirect.dependabot.com/avast/gradle-docker-compose-plugin/issues/361";>#361</a>)</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/601218ab0079a3fd8978efe337b66e7f416ae39c";><code>601218a</code></a> feat: MacOS-specific defaults for executable and dockerExecutable removed</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/a6afb552f505ed1efcbcc28bea9a7bc2bd88a86c";><code>a6afb55</code></a> docs: correct set of projectName in Kotlin DSL example</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/c4a7e8e1b4bc06e4ad500358fbdd6b13610f54ca";><code>c4a7e8e</code></a> feat: <code>isRequiredBy</code> changed in order not to break configuration avoidance (#...</li> <li>Additional commits viewable in <a href="https://github.com/avast/gradle-docker-compose-plugin/compare/0.14.12...0.16.9";>compare view</a></li> </ul> </details> <br /> [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
