ci upgrade

[mpetuska]

• Multiplatform tests
• Automatic snapshot version releases and bumps
• Full releases are now triggered by creating a GH release with tag x.y.z
• Dokka publication to gh pages on full release

[mpetuska]

Before merging this will need branch protection rule update to expect the new builds.

[mpetuska]

tl;dr of automatic version bumps?

In short it basically works as follows:

• When stuff is committed/merged to master or a new tag is created (via gh release) release build runs
• Within release build there's a call to resolve-version build
• resolve-version build reads the ref, tag and gradle.properties and figures out the desired version
• If the desired version is SNAPSHOT (i.e. gradle.properties version won) it publishes snapshot builds to gh packages and maven central
• If the version is NOT snapshot (i.e. tag ref won)
  • It publishes release builds to GH packages and maven central.
  • It bumps patch version of the resolved version and makes it SNAPSHOT (i.e. x.y.<z+1>-SNAPSHOT)
  • Then it writes that new SNAPSHOT version to gradle.properties and pushes it back to the master branch

There are some more minor caveats to this, but that's how it works in a nutshell.

[mpetuska]

Before merging this will need branch protection rule update to expect the new builds.

@patjackson52 can you sort this out, please? Old test and ktlint builds will never start on this PR because they're no longer there :grin:

[patjackson52]

Before merging this will need branch protection rule update to expect the new builds.

@patjackson52 can you sort this out, please? Old test and ktlint builds will never start on this PR because they're no longer there 😁

updated rules - manually merged this one as the checks weren't updating - everything passed