Skip to content

Conversation

@SethTisue
Copy link
Collaborator

@SethTisue SethTisue commented Feb 4, 2025

it's time, I think. (this was originally built for a customer for use on 2.12, but that customer has since moved to 2.13)

@jackkoenig unless you're using it on 2.12? in which case I wouldn't mind leaving this in place. keeping 2.12 isn't causing trouble, exactly, I'd just like to keep the repo easy to keep up to date and easy to work on, even though little work is currently happening

Copy link
Contributor

@jackkoenig jackkoenig left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We're on 2.13 so no problems for us there.

Adding Scala 3 support would be stellar but I suspect that's not in the cards 🙂

@SethTisue
Copy link
Collaborator Author

SethTisue commented Feb 4, 2025

Adding Scala 3 support would be stellar but I suspect that's not in the cards

Yeah, there is not currently any concrete prospect of that.

But I've opened #270 so at least there's a place to discuss what would be involved.

@SethTisue SethTisue merged commit 3892e1b into lightbend-labs:main Feb 4, 2025
6 checks passed
@SethTisue SethTisue deleted the drop-scala-2.12 branch February 4, 2025 04:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

2 participants