Skip to content

Bump gradle-docker-compose-plugin from 0.15.2 to 0.16.9 in /buildSrc#3

Closed
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/gradle/buildSrc/com.avast.gradle-gradle-docker-compose-plugin-0.16.9
Closed

Bump gradle-docker-compose-plugin from 0.15.2 to 0.16.9 in /buildSrc#3
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/gradle/buildSrc/com.avast.gradle-gradle-docker-compose-plugin-0.16.9

Conversation

@dependabot
Copy link

@dependabot dependabot bot commented on behalf of github Oct 19, 2022

Bumps gradle-docker-compose-plugin from 0.15.2 to 0.16.9.

Release notes

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

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

Commits
  • 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
  • 4a013c0 chore(deps): update plugin com.gradle.plugin-publish to v1 (#361)
  • 601218a feat: MacOS-specific defaults for executable and dockerExecutable removed
  • a6afb55 docs: correct set of projectName in Kotlin DSL example
  • c4a7e8e feat: isRequiredBy changed in order not to break configuration avoidance (#...
  • Additional commits viewable in compare view

Dependabot compatibility score

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 use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

Bumps [gradle-docker-compose-plugin](https://github.com/avast/gradle-docker-compose-plugin) from 0.15.2 to 0.16.9.
- [Release notes](https://github.com/avast/gradle-docker-compose-plugin/releases)
- [Commits](avast/gradle-docker-compose-plugin@0.15.2...0.16.9)

---
updated-dependencies:
- dependency-name: com.avast.gradle:gradle-docker-compose-plugin
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Oct 19, 2022

The following labels could not be found: dependabot, dependencies.

As a result, Dependabot will now only use the following labels for PRs: .

@github-actions
Copy link

Gradle Check (Jenkins) Run Completed with:

  • RESULT: null ❌
  • URL:
  • CommitID: 0fa5f6b

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Nov 14, 2022

Superseded by #28.

@dependabot dependabot bot closed this Nov 14, 2022
@dependabot dependabot bot deleted the dependabot/gradle/buildSrc/com.avast.gradle-gradle-docker-compose-plugin-0.16.9 branch November 14, 2022 08:18
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.

0 participants