Andrew Parmet

Of course - I hadn't actually clicked through. Do we know which property should be trusted? Based on the [metadata model](https://maven.apache.org/ref/3.6.3/maven-repository-metadata/repository-metadata.html) I'd say we probably want `metadata.versioning.release`?

I had some trouble getting Buf to work as part of a call to the protobuf-gradle-plugin - linting worked, but I couldn't work out how to check schema backwards compatibility....

FWIW I have my plugin calling Docker in GitHub Actions CI and it seems to work fine. The Protobuf Gradle Plugin doesn't allow plugin options to be passed - it's...

Given an artifact containing an executable it should be possible to adapt the plugin I've written to use it if that's a path you want to pursue, similar to protobuf-gradle-plugin...

Gradle can do this dependency resolution using a custom Ivy repository: https://github.com/andrewparmet/buf-gradle-plugin/blob/main/src/main/kotlin/com/parmet/buf/gradle/BufSupport.kt#L25 `buf-gradle-plugin` no longer requires Docker and resolves Buf executables as Gradle artifacts. If it looks like it might...

I was just bitten by this in my Buf Gradle plugin integration. The way the plugin works is that it uses Buf to create a JSON image and then breakage...

I think I'm following what you're saying, but there's still a piece I don't understand. The `--against` image I'm using was built from with the same `buf.yaml` as the local...

We've sort of dealt with this problem for our own protobuf plugin for Kotlin. Our generator actually publishes the well-known types itself. Downstream projects pull in the generated source along...

Yeah, looks like Google's JS generator also simply generates everything, so I'm not sure this is really addressable. Thanks!

Fair enough. We chose to call that module "core" because the protobuf JAR that we used to generate it contains the definitions for the well-known types in `wrappers.proto` as well...