googleapis / gapic-generator

Tools for generating API client libraries from API Service Configuration descriptions.
Apache License 2.0
303 stars 129 forks source link

chore(deps): update dependency com.google.protobuf:protobuf-gradle-plugin to v0.8.17 #3346

Closed renovate-bot closed 2 years ago

renovate-bot commented 3 years ago

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
com.google.protobuf:protobuf-gradle-plugin 0.8.10 -> 0.8.17 age adoption passing confidence

Release Notes

google/protobuf-gradle-plugin ### [`v0.8.17`](https://togithub.com/google/protobuf-gradle-plugin/releases/v0.8.17) #### Fixed bugs - Fix configuration caching violation when generating jar plugin trampoline script by using saved ProjectLayout to get build directory in GenerateProtoTask ([#​509](https://togithub.com/google/protobuf-gradle-plugin/issues/509)) #### Improvements - Make IDEA support work out of the box with lazy lookup of the IDEA plugin ([#​506](https://togithub.com/google/protobuf-gradle-plugin/issues/506)) #### Thanks to contributors - [@​ALikhachev](https://togithub.com/ALikhachev) - [@​oehme](https://togithub.com/oehme) ### [`v0.8.16`](https://togithub.com/google/protobuf-gradle-plugin/releases/v0.8.16) #### Fixed bugs - Make compileProtoPath variant selection criteria tighter by adding JAVA_RUNTIME usage attribute. Without this, dependency resolution may result in ambiguous variant selection error if the dependency exposes variants with different usages ([#​489](https://togithub.com/google/protobuf-gradle-plugin/issues/489)) - Add explicit DuplicatesStrategy as required by Gradle 7+ ([#​487](https://togithub.com/google/protobuf-gradle-plugin/issues/487)) #### Improvements - Mark generated code as "generated" folder in IDEA, so that users will get warned if they try to edit those files ([#​477](https://togithub.com/google/protobuf-gradle-plugin/issues/477)) - Support outputting generated code directly into JAR/ZIP ([#​480](https://togithub.com/google/protobuf-gradle-plugin/issues/480)) #### Thanks to contributors - [@​oehme](https://togithub.com/oehme) - [@​karuppiah7890](https://togithub.com/karuppiah7890) - [@​tom-haines](https://togithub.com/tom-haines) ### [`v0.8.15`](https://togithub.com/google/protobuf-gradle-plugin/releases/v0.8.15) #### Fixed bugs - Added missing `proto{}` Kotlin DSL for Android builds configuring proto source directory ([#​443](https://togithub.com/google/protobuf-gradle-plugin/issues/443)). #### Improvements - Undeclared configuration-time system property or file reads have been eliminated, this plugin is fully compliant with Gradle configuration caching ([#​467](https://togithub.com/google/protobuf-gradle-plugin/issues/467)). - Avoid running ProtobufExtract tasks if unrelated files change ([#​452](https://togithub.com/google/protobuf-gradle-plugin/issues/452)). #### Thanks to contributors - [@​gavra0](https://togithub.com/gavra0) ### [`v0.8.14`](https://togithub.com/google/protobuf-gradle-plugin/releases/v0.8.14) ##### Fixed bugs - Link only generated Java and Kotlin to compilation task by default ([#​375](https://togithub.com/google/protobuf-gradle-plugin/issues/375)). Fixes the issue in projects with no Java/Kotlin code (with Java plugin applied, maybe implicitly, such as the Scala plugin) that compileJava task is triggered with "no source files" error. - Support packaging and extracting protos in Android aar ([#​440](https://togithub.com/google/protobuf-gradle-plugin/issues/440), [#​443](https://togithub.com/google/protobuf-gradle-plugin/issues/443)). Functionalities of importing protos from Android AAR dependencies is broken in the previous release. It is fixed now. - Avoid storing variantName property in the task ([#​448](https://togithub.com/google/protobuf-gradle-plugin/issues/448)). Fixes the issue of internal warning being triggered by Gradle's configuration caching trying to serialize properties in GenerateProtoTask. ##### Thanks to contributors - [@​gavra0](https://togithub.com/gavra0) ### [`v0.8.13`](https://togithub.com/google/protobuf-gradle-plugin/releases/v0.8.13) ##### New features - This plugin now partially supports Gradle configuration cache (requires Gradle 6.6+). It works to some extent, but there are still problems. ([#​406](https://togithub.com/google/protobuf-gradle-plugin/issues/406), [#​408](https://togithub.com/google/protobuf-gradle-plugin/issues/408), [#​413](https://togithub.com/google/protobuf-gradle-plugin/issues/413)) - Added support for using JAR protoc plugins. ([#​423](https://togithub.com/google/protobuf-gradle-plugin/issues/423)) ##### Fixed bugs - Fixed the breakage for setting DescriptorSetOptions.path with a string literal in Kotlin DSL. ([#​394](https://togithub.com/google/protobuf-gradle-plugin/issues/394)) ##### Improvements - Improved support for Android library projects by packaging proto files into Android archives (.aar). ([#​414](https://togithub.com/google/protobuf-gradle-plugin/issues/414)) - Update: this is still broken in 0.8.13 release, the next release should fix it. ##### Thanks to contributors - [@​rpalcolea](https://togithub.com/rpalcolea) - [@​kazuki-ma](https://togithub.com/kazuki-ma) - [@​gavra0](https://togithub.com/gavra0) - [@​eskatos](https://togithub.com/eskatos) - [@​stoyicker](https://togithub.com/stoyicker) - [@​enbandari](https://togithub.com/enbandari) - [@​dcabasson](https://togithub.com/dcabasson) ### [`v0.8.12`](https://togithub.com/google/protobuf-gradle-plugin/releases/v0.8.12) ##### Fixed bugs - Always include extract protos in compiled archive. ([#​389](https://togithub.com/google/protobuf-gradle-plugin/issues/389)) Previously processResourcesTask runs in parallel with extractProtoTasks, which would potentially lead to Jars without including protos from dependencies. ##### Improvements - The plugin now is compatible with Gradle 6.1 [Instant Execution](https://gradle.github.io/instant-execution/). ([#​381](https://togithub.com/google/protobuf-gradle-plugin/issues/381)) ##### Thanks to contributors - [@​eskatos](https://togithub.com/eskatos) - [@​jd3nn1s](https://togithub.com/jd3nn1s) ### [`v0.8.11`](https://togithub.com/google/protobuf-gradle-plugin/releases/v0.8.11) ##### Compatibility changes - The plugin now requires Gradle 5.6+ (corresponding Android plugin version is 3.5.0+ if using for Android). ##### Fixed bugs - Fixed issue of consumer projects not being able to extract proto files from `implementation` dependencies that use `java-library` plugin. ([#​366](https://togithub.com/google/protobuf-gradle-plugin/issues/366)) ##### Dependencies - Bumped `osdetector` plugin version to `1.6.2`. - Bumped Guava version to `27.0.1-jre`. ##### Improvements - Support protobuf plugins with artifacts that have no extension. ([#​335](https://togithub.com/google/protobuf-gradle-plugin/issues/335)) - The plugin now is able to work with Gradle 6.0. ([#​364](https://togithub.com/google/protobuf-gradle-plugin/issues/364), [#​365](https://togithub.com/google/protobuf-gradle-plugin/issues/365)) ##### Documentation - Updated documentation for using protobuf javalite code generation option for protobuf version after `3.8.0`. ([#​323](https://togithub.com/google/protobuf-gradle-plugin/issues/323)) ##### Thanks to contributors - [@​kshithijiyer](https://togithub.com/kshithijiyer) - [@​stkent](https://togithub.com/stkent) - [@​lptr](https://togithub.com/lptr) - [@​eskatos](https://togithub.com/eskatos)

Configuration

📅 Schedule: "after 9am and before 3pm" (UTC).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Renovate will not automatically rebase this PR, because other commits have been found.

🔕 Ignore: Close this PR and you won't be reminded about this update again.



This PR has been generated by WhiteSource Renovate. View repository job log here.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 3 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 2 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 2 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

gcf-merge-on-green[bot] commented 2 years ago

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

forking-renovate[bot] commented 2 years ago

Renovate Ignore Notification

As this PR has been closed unmerged, Renovate will now ignore this update (0.8.17). You will still receive a PR once a newer version is released, so if you wish to permanently ignore this dependency, please add it to the ignoreDeps array of your renovate config.

If this PR was closed by mistake or you changed your mind, you can simply rename this PR and you will soon get a fresh replacement PR opened.