Switch to GitHub actions + and publish to maven central using sbt-ci-release

[mkurz]

• Fixes Publish to Maven central #1

@johanandren What you need to do:

1. Add the git tag 0.1 to 58b9cde (because you never did that)
2. Add SONATYPE_USERNAME, SONATYPE_PASSWORD, PGP_PASSPHRASE and PGP_SECRET to this repos "Repository secrets" as described here
3. Merge this pull request
4. Watch how a new snapshot gets published here: https://github.com/johanandren/sbt-akka-version-check/actions/workflows/publish.yml
5. If a snapshot got published successfully you can then try to release the next version to maven central by tagging 0.2

[johanandren]

Thanks, I think I'd need to change the groupId of this project as well, If I publish it on my own. But I can add that on top of the changes you've shared here before merging.

[mkurz]

Thanks @johanandren! Actually Play 2.9 depends on this plugin, so we finally have all our dependencies hosted on maven central 👍

[johanandren]

I see, does that mean I must republish 0.1 with the original organization/groupId or is it fine to switch (com.markatta is my private groupId)?

[mkurz]

The switch is fine, I will just upgrade in Play to make use of the new one.

[mkurz]

@johanandren Told scala steward about the switch as well:

• Migrate sbt-akka-version-check scala-steward-org/scala-steward#3272

[johanandren]

Thanks!