Sam Garfinkel

Where is this 3.2 release available? Crnk really should comply with the best practices outlined in Semver: https://semver.org/ Can releases please also be deployed to MavenCentral?

@ajoberstar That's exactly what I'd like. There's a lot of times I might have a snapshot release living in master, which might be several commits ahead of the last stable...

@ajoberstar Is there any way to do this temporarily with a buildSrc script? It looks like a lot of API is private or package private.

`npm i nodegit@next` works for Node 16 (seems there's a pending PR to resolve some lingering issue on Node 18, though).

@blaggacao That issue is closed and PR merged. Is this just a matter of updating the dependency version in the repo?

Should probably provide X-Ray publishing integration with Spring Cloud Sleuth (via a Zipkin publisher?) as well. Could knock out both as part of #389

Would it be better to instead integrate opentracing? It would support more tracing backends.

Just as an FYI, Brave supports instrumentation of AWS SDK v1 and v2 out of the box https://github.com/openzipkin/zipkin-aws/tree/master/brave/instrumentation-aws-java-sdk-v2-core. You can use this until a higher level integration is supported by...

The latest versions of the SDK allows you to return an `SdkPublisher` (which extends `Publisher`) which you can use to map to the underlying byte array: https://sdk.amazonaws.com/java/api/latest/software/amazon/awssdk/core/internal/async/PublisherAsyncResponseTransformer.html. The main issue...

Sure, the use case is basically what this loader does: https://www.npmjs.com/package/resolve-url-loader SASS often leaves relative URLs that are unresolvable in the final built CSS because they are meant to be...