-
Notifications
You must be signed in to change notification settings - Fork 34
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrade to MUnit 1.0.0-M6 #223
Changes from all commits
974242f
df9cd7d
ba30103
b58baef
4ab5125
88db7d7
824f091
98ecf06
b54943a
cd8357d
2af08f7
b91180c
c1e74ca
f8492ca
146426a
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,77 +1,24 @@ | ||
ThisBuild / tlBaseVersion := "1.0" | ||
ThisBuild / tlBaseVersion := "2.0" | ||
|
||
ThisBuild / developers += tlGitHubDev("milanvdm", "Milan van der Meer") | ||
ThisBuild / startYear := Some(2021) | ||
|
||
ThisBuild / crossScalaVersions := List("3.1.3", "2.12.16", "2.13.8") | ||
|
||
ThisBuild / tlFatalWarningsInCi := false | ||
|
||
lazy val docs = project | ||
.in(file("site")) | ||
.dependsOn(ce3.jvm) | ||
.dependsOn(core.jvm) | ||
.enablePlugins(TypelevelSitePlugin) | ||
|
||
lazy val root = tlCrossRootProject.aggregate(ce3, ce2) | ||
lazy val root = tlCrossRootProject.aggregate(core) | ||
|
||
lazy val ce3 = crossProject(JSPlatform, JVMPlatform) | ||
.crossType(CrossType.Full) | ||
.settings( | ||
name := "munit-cats-effect-3", | ||
Compile / unmanagedSourceDirectories += baseDirectory.value / "../../common/shared/src/main/scala", | ||
Test / unmanagedSourceDirectories += baseDirectory.value / "../../common/shared/src/test/scala" | ||
) | ||
lazy val core = crossProject(JSPlatform, JVMPlatform) | ||
.crossType(CrossType.Pure) | ||
.in(file("core")) | ||
.settings( | ||
name := "munit-cats-effect", | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We should make sure to register a Scala Steward migration for |
||
libraryDependencies ++= Seq( | ||
"org.scalameta" %%% "munit" % "0.7.29", | ||
"org.scalameta" %%% "munit" % "1.0.0-M6", | ||
"org.typelevel" %%% "cats-effect" % "3.3.14" | ||
), | ||
// we are checking binary compatibility from the 1.0.6 version | ||
mimaPreviousArtifacts ~= { | ||
_.filter { m => | ||
VersionNumber(m.revision).matchesSemVer(SemanticSelector(">=1.0.6")) | ||
} | ||
} | ||
) | ||
.jvmSettings( | ||
Compile / unmanagedSourceDirectories += baseDirectory.value / "../../common/jvm/src/main/scala", | ||
Test / unmanagedSourceDirectories += baseDirectory.value / "../../common/jvm/src/test/scala" | ||
) | ||
.jsSettings( | ||
Compile / unmanagedSourceDirectories += baseDirectory.value / "../../common/js/src/main/scala", | ||
Test / unmanagedSourceDirectories += baseDirectory.value / "../../common/js/src/test/scala", | ||
scalaJSLinkerConfig ~= (_.withModuleKind(ModuleKind.CommonJSModule)) | ||
) | ||
|
||
lazy val ce2 = crossProject(JSPlatform, JVMPlatform) | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. If we decided to make EOL the whole library ("munit-cats-effect-2"), I argue it should be described in docs. As well as changing There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Yes, it should be described in docs. But if we make those changes in this PR, then it will go live as soon as it merges even before official release. Maybe should make a new branch for me to target my changes to, instead of main? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we already can slice changes on removing CE2 support into another PR and merge it as soon as possible (because no things we should do after it) 👍🏻 There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Good plan, I will prepare it shortly. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Aww. Probably I was wrong here. I was thinking we want to deprecate the whole library. Because we integrate There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Haha, I see. Actually that was how this library started but it is better it remains independent. Origin story: There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Okay, but why not deprecate the CE2-based library? Speaking as one of the http4s maintainers, it'd be totally fine. Because I'm confident, here we integrate precisely There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should just EOL 1.x when 2.x is released. And 2.x won't support CE2 at all. |
||
.crossType(CrossType.Full) | ||
.settings( | ||
name := "munit-cats-effect-2", | ||
Compile / unmanagedSourceDirectories += baseDirectory.value / "../../common/shared/src/main/scala", | ||
Test / unmanagedSourceDirectories += baseDirectory.value / "../../common/shared/src/test/scala" | ||
) | ||
.settings( | ||
libraryDependencies ++= Seq( | ||
"org.scalameta" %%% "munit" % "0.7.29", | ||
"org.typelevel" %%% "cats-effect" % "2.5.5" | ||
), | ||
// we are checking binary compatibility from the 1.0.6 version | ||
mimaPreviousArtifacts ~= { | ||
_.filter { m => | ||
VersionNumber(m.revision).matchesSemVer(SemanticSelector(">=1.0.6")) | ||
} | ||
} | ||
) | ||
) | ||
.jvmSettings( | ||
Compile / unmanagedSourceDirectories += baseDirectory.value / "../../common/jvm/src/main/scala", | ||
Test / unmanagedSourceDirectories += baseDirectory.value / "../../common/jvm/src/test/scala" | ||
) | ||
.jsSettings( | ||
libraryDependencies += "org.scala-js" %%% "scala-js-macrotask-executor" % "1.0.0", | ||
Compile / unmanagedSourceDirectories += baseDirectory.value / "../../common/js/src/main/scala", | ||
Test / unmanagedSourceDirectories += baseDirectory.value / "../../common/js/src/test/scala", | ||
scalaJSLinkerConfig ~= (_.withModuleKind(ModuleKind.CommonJSModule)) | ||
) | ||
|
||
addCommandAlias("fmt", """scalafmtSbt;scalafmtAll""") | ||
addCommandAlias("fmtCheck", """scalafmtSbtCheck;scalafmtCheckAll""") |
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
This file was deleted.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are we really want to do a new major release based on the fifth milestone?..
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Bumping the base version doesn't mean a new major release, it means we are starting the 2.x series of development that is not compatible with any 1.x release. I propose we publish this PR as 2.0.0-M1
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Further reading: https://typelevel.org/sbt-typelevel/faq.html#what-is-a-base-version-anyway
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, I just was confused with this reference to
2.0.0
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Haha yes, we always debate the correct deprecation version for http4s too :) I don't really care, I will happily put whatever you want there.