search

logzio / micrometer-registry-logzio

Apache License 2.0
0 stars 0 forks source link

Bump com.google.protobuf:protobuf-gradle-plugin from 0.8.13 to 0.9.4 #10

Open dependabot[bot] opened 4 months ago

dependabot[bot] commented 4 months ago

Bumps com.google.protobuf:protobuf-gradle-plugin from 0.8.13 to 0.9.4.

Release notes

Sourced from com.google.protobuf:protobuf-gradle-plugin's releases.

v0.9.4 is released

  • Fix a bug that codegen plugins from system search path no longer works. (#675)
  • Avoid duplicate GenerateProtoTask output dir. This causes tasks to fail if it depends on the output source and duplicationStrategy is set to DuplicatesStrategy.FAIL. (#718)
  • Avoid eagerly resolving input files in ProtobufExtract. This bug would cause a lot of invalidations of configuration cache when upgrading to Gradle 8.1. (#719)
  • Fix plugin compatibility with Kotlin Gradle Plugin 1.9.0 release. (#721)

v0.9.3 is released

  • Fix "KotlinCompile is not a subclass of the given type org.gradle.api.tasks.SourceTask" regression in 0.9.2 (#657)
  • Fix configuration cache incompatibility with Gradle 8.1 with GenerateProtoTask.getIsTest() in the stack trace (#692)
  • Avoid eager reading of buildDir (#678). buildDir reading is now delayed until task configuration, so care is still needed if you modify buildDir.
  • Upgrade osdetector-gradle-plugin to 1.7.3. This adds detection for loongarch64 and avoids calling Provider.forUseAtConfigurationTime() for Gradle >= 7.4

v0.9.2 is released

Fixed bugs

  • Avoid circular dependencies with other plugins by manually plumbing the test dependency on main instead of using the compile classpath (#631). Fixes #624, a regression introduced in 0.9.0
  • Emulate and deprecate generatedFilesBaseDir (#636). generatedFilesBaseDir no longer changes the output directory directly. Instead, the default directory is always used and files are copied to generatedFilesBaseDir. This allows the task to delete previous output before generating new output. Users of generatedFilesBaseDir should stop using the configuration and instead use a separate Copy or Sync task. Fixes #33 where generated code of old builds remains, for users not using generatedFilesBaseDir
  • Set default command length limit to 64k (#653). Fixes argument list too long on Mac OS (#633)

v0.9.1 is released

Fixed bugs

  • Fixed a regression from 0.8.x where the proto source set filters were not being applied, causing non-.proto files to be passed to protoc (#621). This fixes errors of the form No syntax specified for the proto file: where the file listed is not a .proto file.

v0.9.0 is released

Fixed bugs

  • Workaround provider bug in Gradle when excluding tasks (#576). Errors were of the form Querying the mapped value of provider(interface java.util.Set) before task ':project:processResources' has completed is not supported

Improvements

  • Improved Kotlin accessor support for Android Gradle Plugin 7.x, which uses a different SourceSet class (#565, fixes #540)
  • Migrated project.protobuf from a convention to an extension (#577). This greatly improves the Kotlin experience, as fewer imports are necessary. On upgrade, kts users will need to remove any now-unnecessary imports from their scripts
  • Significantly improve support for task configuration avoidance. README.md has not yet been updated to encourage using configureEach instead of each within generateProtoTasks {}, but it is beneficial as long as you are not using any IDE plugins
  • Added generated code to java SourceSet instead of only adding it to JavaCompile and related tasks. This should cause tasks like sourcesJar and javadoc to now include the generated code. You may need to exclude the generated code from linters
  • Added Eclipse and VSCode support (#590). They should no longer have trouble finding generated code
  • Removed references to unused Gradle-internal FileResolver (#595)
  • Removed usage of deprecated GUtil (#604)
  • Removed dependency on Apache commons-lang (#606)
  • Removed dependency on Guava (#609)
  • Upgraded osdetector-gradle-plugin to 1.7.1
  • Substantial internal modernization. This should not impact most users, but there is risk of a regression or observing timing differences.

Thanks to contributors

v0.8.19 is released

The coordinates of the plugin have changed (inadvertently, same as in gradle/plugin-portal-requests#124). If you are not using the plugin DSL, then you will need to change the dependency classpath from gradle.plugin.com.google.protobuf:protobuf-gradle-plugin to com.google.protobuf:protobuf-gradle-plugin when upgrading. I hope that's the only issue. I would fix it with another release, but it seems this is how Gradle wants it, because plugin-publish is removing an override.

Fixed bugs

  • Fixed issue that would warn of google/protobuf-gradle-plugin#248 with Android, even when it didn't make sense (#542). The plugin itself was at fault
  • Fixed path-based protoc/plugin binaries to be considered for out-of-date checking (#560)

... (truncated)

Commits
  • 32afa9e 0.9.4 release
  • a7c26cb Fix plugin compatibility with Kotlin Gradle Plugin 1.9.0 release (#715) (#721)
  • 5c15781 stop using configuration Configuration#fileCollection(Dependency...), soon to...
  • 4502c7e Avoid eagerly resolving input files in ProtobufExtract (#713) (#719)
  • 30fa504 Avoid duplicate GenerateProtoTask output dir (#703) (#718)
  • 1c33cad README: clarify plugins search path (#702) (#717)
  • 6673571 Support plugins without an ExecutableLocator
  • 0a2c7bb Start 0.9.4 development cycle
  • b4ee4a7 0.9.3 release
  • 2ca308b remove jcenter add maven central (#698)
  • 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 show 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)