scala3-migrate VS sbt-ci-release

> If I recall, there's a compiler plugin they put out that could automatically make many of those changes

Actually, there are compiler options to rewrite the sources to/from scala3, I have tried this in more complex projects and it worked nicely (see https://docs.scala-lang.org/scala3/guides/migration/tooling-...)

This is the link to the plugin you mentioned which is supposed to avoid the manual syntax updates but I haven't had the need to try it, like you said, most of the times the changes are trivial enough (https://docs.scala-lang.org/scala3/guides/migration/scala3-m...).

> An example of one of the programmable games in action

This comes handy to me, looks cool! For one or another reason, I ended up in this page which seems to intend hosting the same app but it doesn't work, just wanted to let you know (https://www.wbillingsley.com/lavamaze)

There is a similar nice project which I have been looking into (https://www.kogics.net/kojo).

I'm using scala3-migrate as reference, although I haven't really done any Scala that much to know that issues this has.

I'm a bit surprised to see sbt-ci-release (https://github.com/sbt/sbt-ci-release) not even mentioned. It's widely used for this.

The sooner JARs are on Maven, the better for all of us. With https://github.com/sbt/sbt-ci-release/ publishing is sooo easy.

The first thing you must try is running sbt publishLocal then, you should be able to depend on the artifact from another project, when that works, you will likely want to publish the artifacts somewhere, maven central is the most popular way but it requires some setup, you can use https://github.com/sbt/sbt-ci-release to auto-publish on new commits (it explains how to get a sonatype account), github-packages is very handy but it requires a github access token to pull the packages (https://github.com/djspiewak/sbt-github-packages).

> Veautiful - https://www.wbillingsley.com/veautiful/

Thanks for sharing, first time I see this project mentioned.

> Any day now, I'll get a chance to improve the documentation of the framework (and give it a proper release rather than using JitPack snapshots all the time).

It is worth commenting about https://github.com/sbt/sbt-ci-release which makes it simple to auto-publish to maven central.

Use https://github.com/sbt/sbt-ci-release

sbt-ci-release is a great one-stop shop for this. It handles sbt-pgp, sbt-release and sbt-sonatype for you, so you don't have to configure them individually yourself. The readme also has an easy to follow tutorial.