Skip to content

for Scala 3 users, require Scala 3.1+#547

Merged
SethTisue merged 1 commit intoscala:mainfrom
SethTisue:drop-scala-3.0
Jul 8, 2022
Merged

for Scala 3 users, require Scala 3.1+#547
SethTisue merged 1 commit intoscala:mainfrom
SethTisue:drop-scala-3.0

Conversation

@SethTisue
Copy link
Copy Markdown
Member

@SethTisue SethTisue commented Jul 8, 2022

as per scala/scala-lang#1387, there's no longer any need to keep supporting Scala 3.0.x. it's fine to expect people to upgrade to 3.1 or higher

Admittedly I'm making a bit of an executive decision here. But I see this happening in many places in the ecosystem.

Also, it simplifies the build. Scala 3.0.x didn't support Scala Native, so we had to do weird stuff to publish for 3.0 on JS and JVM but 3.1 on Native. This removes those complications.

@SethTisue SethTisue force-pushed the drop-scala-3.0 branch 2 times, most recently from eeb1349 to 750c233 Compare July 8, 2022 23:16
as per scala/scala-lang#1387, there's no longer any need
to keep supporting Scala 3.0.x. it's fine to expect people
to upgrade to 3.1 or higher
@SethTisue SethTisue merged commit a6d5f2f into scala:main Jul 8, 2022
@SethTisue SethTisue deleted the drop-scala-3.0 branch July 8, 2022 23:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant