[main] Fix play-scala-isolated-slick-example test for Scala 3 (backport #913) by @mkurz - #915
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
After the
reloadthe Scala version gets set back to the default again.So when running tests for Scala 3, having
MATRIX_SCALA=3.xafter the reload we are on Scala 2.13.x again...I found this because I wanted to test Scala 3.3.7-RC2 locally and only published Play for that Scala 3 version and this test complained it can not find the 2.13.x artifacts...
This is an automatic backport of pull request #913 done by Mergify.