Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Please publish for Scala 2.13.0-RC1
See original GitHub issuehttps://github.com/dispatch/reboot/issues/210 depends on net.liftweb#lift-json to be available for Scala 2.13.0-M5.
Issue Analytics
- State:
- Created 5 years ago
- Comments:16 (13 by maintainers)
Top Results From Across the Web
2.13.0-RC1 timing: January 2019 - Scala Contributors
We've decided to postpone the 2.13.0-RC1 release by 3 months (from mid October to mid January), to make sure that we have enough...
Read more >Scala 2.13.5 planning - Announcements
This thread is for updates and discussions about an eventual Scala 2.13.5 ... We'll wait for 3.0.0-RC1 to be released, and then we'll...
Read more >2.13.0-M5 release train - Announcements - Scala Contributors
It's just about time to roll another milestone, the last one before 2.13.0-RC1. We aim to build M5 this week. ... and please...
Read more >All Available Versions - The Scala Programming Language
Released on November 7, 2022 · Current 2.13.x release: 2.13.10. Released on October 13, 2022 ... Scala 2.13.0-RC1 · Scala 2.13.0-M5 · Scala...
Read more >Scala3-migrate: a tool making it easier to migrate to Scala 3
As of today, project leads will publish the road-maps under the category ... This tool targets projects that aim to cross-compile in scala...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Well, the compelling reason is that consumers of the library can prepare their transition to Scala 2.13.0. If not for M5, a good point will be RC1. Since Scala 2.13.0 comes with API change (new collections), the transition process is a bit more work than just relying on source compatibility. Identifying problems with the new collections API early will be generally helpful. Thanks!
Just want to re-iterate that we’d be open to this. We actually publish snapshots on each master merge so all we’d need to do is get this building in master.