dependabot[bot] opened a new pull request, #28465: URL: https://github.com/apache/beam/pull/28465
Bumps [com.avast.gradle:gradle-docker-compose-plugin](https://github.com/avast/gradle-docker-compose-plugin) from 0.16.12 to 0.17.5. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/avast/gradle-docker-compose-plugin/releases";>com.avast.gradle:gradle-docker-compose-plugin's releases</a>.</em></p> <blockquote> <h2>0.17.5</h2> <p>Docker Compose 2.21.0 introduced a breaking change in <code>docker compose ps</code> output format, this release adds support for the new format (while supporting also the old format).</p> <h2>0.17.4</h2> <p>Ensure the <code>-f</code> parameters go right after <code>docker compose</code>.</p> <h2>0.17.3</h2> <p>Revert of a change introduced in 0.17.0 that introduced stderr reading when executing <code>docker</code> command. It leads to an unexpected output if Docker is not fully correctly installed and prints warnings to stderr (while stdout is valid).</p> <h2>0.17.2</h2> <p>Safer JSON parsing of <code>docker compose ps</code> output.</p> <h2>0.17.1</h2> <p>Update to Gradle v8.</p> <h2>0.17.0</h2> <ul> <li>Migrated to the latest Gradle 7.x</li> <li>As Docker Compose V1 is deprecated, default value of <code>useDockerComposeV2</code> property was changed from <code>false</code> to <code>true</code>, so <code>docker compose</code> is used by default (instead of <code>docker-compose</code>).</li> <li>More version formats handled in the <code>VersionNumber.parse</code> method.</li> <li>Durations stripped from cache key.</li> </ul> <h2>useDockerComposeV2 introduced</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/cd6e3d7758c1dee0c515ac35d2f417e0d7bed887";><code>cd6e3d7</code></a> fix: Compose 2.21.0 returns newline-separated JSONs instead of single JSON ar...</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/fdc7e461bc9f5fa052437e6ad323f367579adf1f";><code>fdc7e46</code></a> chore(deps): update actions/checkout action to v4</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/0aaf6181bce4528e791421dc91c955511da91636";><code>0aaf618</code></a> fix(deps): update dependency org.yaml:snakeyaml to v2.2</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/09fac008c7acd7b0691a6fba16e7e50cda57a125";><code>09fac00</code></a> chore(deps): update dependency gradle to v8.3 (<a href="https://redirect.github.com/avast/gradle-docker-compose-plugin/issues/417";>#417</a>)</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/a9402d8f4009a4f16580615c6cb5debf8a992343";><code>a9402d8</code></a> chore(deps): update plugin com.gradle.plugin-publish to v1.2.1 (<a href="https://redirect.github.com/avast/gradle-docker-compose-plugin/issues/416";>#416</a>)</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/101f4ce5fa0bd14e214f1b7059a9a5b40012d811";><code>101f4ce</code></a> fix: -f always comes directly after docker compose Fixes <a href="https://redirect.github.com/avast/gradle-docker-compose-plugin/issues/414";>#414</a></li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/1c4d19476294377e0c0d7b3ae3cada7d947c13bb";><code>1c4d194</code></a> fix: stderr of executed docker command ignored again</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/129275f4d42035645d1e7e4bbf7a19b86e45ee6a";><code>129275f</code></a> fix: safer JSON parsing for cache key</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/c01c75cd9e41788b0db1a6d26152a63b9f9cb7d2";><code>c01c75c</code></a> chore: safer closure call for nested settings</li> <li><a href="https://github.com/avast/gradle-docker-compose-plugin/commit/8912074155e88eb99a6119078cdb6bf46ae785b8";><code>8912074</code></a> chore: Gradle deprecations warnings handled</li> <li>Additional commits viewable in <a href="https://github.com/avast/gradle-docker-compose-plugin/compare/0.16.12...0.17.5";>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 show <dependency name> ignore conditions` will show all of the ignore conditions of the specified dependency - `@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]
