Daniel Esik

Hmmm, it's likely not Coursier, as disabling it changed nothing (`useCoursier := false`) ``` [info] [SUCCESSFUL ] org.typelevel#cats-effect-std_2.13;3.5.7!cats-effect-std_2.13.jar (5342ms) [info] downloading https://repo1.maven.org/maven2/org/scala-lang/scala-compiler/2.13.15/scala-compiler-2.13.15.jar ... [info] [SUCCESSFUL ] org.typelevel#cats-kernel_2.13;2.9.0!cats-kernel_2.13.jar (34119ms) [info] [SUCCESSFUL...

Wow, what luck to catch the Redis4Cats contributor (or maintainer?)! But let’s discuss this in the [appropriate place](https://github.com/profunktor/redis4cats/discussions/955).

@kubukoz yeah but, at the end of the story, having such binary compatibility issues on the end-user side is still weird since the major Cats-Core version was consistent across all...

Thanks for doing this! I like the changes, but it would be beneficial to get a second opinion from someone on the team.

Ah, yes, Mima wouldn't like this. Perhaps this makes sense to 1.0.

I managed to solve the issue by changing a little bit the approach of publishing a website to GH pages — by using external Github Action instead of `mdoc/docusaurusPublishGhpages`. If...

Alright. What if we divide tests into two groups for Native build?

> [error] java.lang.RuntimeException: expected `scalac-profiling/scalaVersion` to be "2.13.12" or later, [error] but found "2.13.10"; upgrade scalaVersion to fix the build. [error] [error] to support backwards-only binary compatibility (SIP-51), [error] the...

Can you share the JVM options set for SBT when running compilation to build flamegraphs data by `scalac-profiling`? There may be a situation where resources are exceeded. However, it's unlikely...

I meant options set for the SBT itself: ``` ❯ sbt -d ... java -Dfile.encoding=UTF-8 -server -XX:ReservedCodeCacheSize=512m ... -Xmx8G ``` Anyway, consider setting quite a significant `Xmx`. But at this...