Add support for Scala 2.13

[danicheg]

Resolves #35

Alongside adding Scala 2.13 support, some other things have been done:

• All upstream libraries have been updated to current versions
• Updated SBT 1.5.0 -> 1.10.0 and all its plugins to up-to-date versions
• Scala 2.12 updated to 2.12.19
• Migrating from tut to mdoc
• Migrated CI from Travis to Github Actions

I tested that PR against Scala 2.12 and Scala 2.13 on JVM and JS platforms. It works fine. The only thing I'm concerned about is that we might have issues with building and publishing the website. I migrated the corresponding SBT plugins according to the docs but failed to bootstrap the site locally. I agree it sounds disappointing, and it might be a blocker for getting this PR merged. However, maybe someone will express interest in putting on the finishing touches, or I will find time to do that.

[danicheg]

As usual, to get the Github Actions Workflows to run, they must be in the master branch 🤷🏻 Meanwhile, I managed to run and debug the CI pipelines (except for publishing, for sure) within my fork, and it appears to be 'green' https://github.com/danicheg/reftree/actions/runs/9627261707/job/26554149707.

[stanch]

This is amazing, thank you so much for breathing life into this project :)

I will be able to take a closer look tomorrow. If it’s not too much trouble to pull all => changes into a separate PR to ease the review, that would be appreciated, but if not that’s ok. (Yes, I drank too much unicode kool-aid back in the day, sorry!)

Don’t worry about the site. Last time I tried Gitbook a few years ago, it was broken already. The solution is to move to Docusaurus and I think I can do that relatively easily.

[danicheg]

If it’s not too much trouble to pull all => changes into a separate PR to ease the review, that would be appreciated, but if not that’s ok.

Unfortunately, these changes are forced by scalac https://github.com/scala/scala/pull/7540. Therefore, putting them in a separate PR would lead to a broken build in Scala 2.13.

The solution is to move to Docusaurus and I think I can do that relatively easily.

Funnily, I also thought about migrating to Docusaurus and decided to discuss this first :)

[stanch]

Therefore, putting them in a separate PR would lead to a broken build in Scala 2.13.

I assumed this PR would then be against the branch of the other PR. But never mind, it’s not a huge obstacle.

[danicheg]

I assumed this PR would then be against the branch of the other PR. But never mind, it’s not a huge obstacle.

Ahh, I see.

[danicheg]

@stanch I know this PR looks monstrous, let me know if I should make it more accessible.

[stanch]

I think it’s fine as it is — my plan is to merge and do some sanity checks on the 2.13 collection instances. I’ll try to find some time tomorrow. Sorry for not being faster, most of my free time is now spent building a chair 😅

[danicheg]

I’ll try to find some time tomorrow. Sorry for not being faster, most of my free time is now spent building a chair

Take your time, no rush at all. Building a chair sounds awesome, especially when you're bored with these damn computers.

[danicheg]

Unfortunately, a miracle hasn't happened, and microsite building/publishing failed. So, let's try to migrate to Docusaurus?

[stanch]

Yeah, I’ll take a stab at that!

[stanch]

@danicheg Check this out: https://github.com/stanch/reftree/commit/37ddf66c969774454abbc4753bf44bc533cf467b.

It’s live: http://stanch.github.io/reftree/docs

I had to make a few concessions to keep my sanity:

• Scaladoc is gone
• Scala.js demo is gone
• Mdoc’s DocusaurusPlugin kept complaining about yarn not being there, so I just bypassed DocusaurusPlugin. Tbh, I am not a fan of using sbt for everything anyway
• The CI scripts are a bit repetitive, but I’m lazy and it works™

Contributions are welcome :P

I’ll likely do a release tomorrow, still need to fix something in the build for that.

[danicheg]

@stanch nicely done!