Daniel Urban

I'm not sure what would that mean in terms of `nativeConfig` in sbt...

With that configuration, there are 2 things: - Our tracing tests fail; I don't know, maybe this is expected? - There is a completely new (to me) failure: https://github.com/typelevel/cats-effect/actions/runs/14412075678/job/40422082896?pr=4362#step:22:1797

About the "new" linker error: there is a warning [previously](https://github.com/typelevel/cats-effect/actions/runs/14412075678/job/40422082896?pr=4362#step:22:1691): ``` [warn] LTO.thin is unstable on MacOS, it can lead to compilation errors. Consider using LTO.full (legacy, slower) or LTO.none...

Thanks for trying! This whole apiMappings setting is very mysterious to me, so I don't have any ideas...

~~Have we seen this setting working _anywhere_? I see that in the scala-js API it seems to work; I suspect that's because it uses the old (JVM 8) url...~~ -...

There is a strange interaction with the `-release` option, but it doesn't seem `sbt-typelevel` specific, so I've opened https://github.com/scala/bug/issues/12820.

Thanks, the artifacts are indeed there now. However, the Scala 3 artifacts seem to have been built with Scala 3.4. Is that intentional? I was under the impression, that libraries...

> It was intentional in the sense that I missed the announcement that libraries should remain on 3.3 😅 Why is that? Well, I actually can't find an announcement :rofl:...

Found the announcement: https://www.scala-lang.org/blog/2024/02/29/scala-3.4.0-and-3.3.3-released.html#-so-which-version-should-i-update-to.

Some more information: the immediate cause seems to be `.withOptimize(false)` in the CE test config. This option causes some `alwaysinline` methods (notably `LockWord.LockType.Inflated`) _not_ to be inlined, and code calling...