Naftoli Gugenheim
Naftoli Gugenheim
Technically my code changes the API, maybe that doesn't warrant a bigger version bump if the old API was wrong? I don't know what the original author had in mind.
@mdedetrich I'm still getting those MissingClassProblem in the compat report table :arrow_up:
Plus, the Java 21 tests are failing with ``` [info] Main Scala API documentation successful. [info] Module slick:3.5.1-pre.5.bfa5428c has no dependency issues with version 3.5.0 (versionPolicyIntention is set to 'Compatibility.BinaryAndSourceCompatible')...
How can this be fixed? Would putting the macro in an object other than ShapedValue solve it?
Looks like it's released in 4.9.1
@Mergifyio rebase
@mdedetrich what's the story?
Perhaps there are some settings that would make fewer changes?
Let's do this after 3.5.0 is released. That way in case a hotfix is needed there are less diffs to go through. But after it's released we can go wild...
By naming the variable that way, isn't that requiring tests to have some knowledge of the build tool? I think `$PORT` is a standard variable, e.g. Google Cloud Run expects...