sbt-dotty: Use default dependency resolution, release 0.4.1

[smarter]

@anatoliykmetyuk With drone I was able to release a new sbt-dotty version by running rone build promote lampepfl/dotty NNNN sbt_release, how do I do that with github-release ? (Switching to making a release when a special tag like sbt-dotty-v... is pushed would be fine too)

[anatoliykmetyuk]

@smarter that command triggered the following command:

  ./project/scripts/sbtPublish ";project sbt-dotty ;publishSigned ;sonatypeBundleRelease"

You can run it locally but you will need to set the following envvars. For PGP_PW/PGP_SECRET you can use your private key.

I think it will be a good idea to make SBT plugins released on tags the same way we release Dotty. E.g. the tag can take the form of sbt_plugin_0.4.1 and this will trigger the plugin publish workflow in GH Actions CI.

[smarter]

You can run it locally but you will need to set the following envvars. For PGP_PW/PGP_SECRET you can use your private key.

I don't want to run it locally. We do all our release via CI to avoid issues with unclean environments, etc, we shouln't stop now. I'll see if the drone ci publish step still works.

I think it will be a good idea to make SBT plugins released on tags the same way we release Dotty. E.g. the tag can take the form of sbt_plugin_0.4.1 and this will trigger the plugin publish workflow in GH Actions CI.

Agreed, can you implement that? (we already have an sbt-dotty-v0.4.0 tag so I would follow this convention).