add the publishing to gpr and release pipeline

[vahidlazio]

• create release per tag created in the main branch.
• we can depend on openfeature sdk in the provider (on any branch/commit as following using jitpack) after merging this :

api("com.github.spotify:openfeature-kotlin-sdk:[BRANCH_NAME]-SNAPSHOT") // or commit hash

or on a release

api("com.github.spotify:openfeature-kotlin-sdk")

[nicklasl]

Is this correct? shouldn't we pull this from somewhere? The tag info for example?

[vahidlazio]

true, we should think about versioning. i was thinking to start with manual versioning for now and have something released using pipeline and then add tickets for versioning. we need to refine them as well and think of a strategy how we want to version our sdks.

[nicklasl]

Yeah, sounds good. Just a note that we have the version duplicated both here and in android { defaultConfig {} }

[fabriziodemaria]

+1 on syncing Github release versions with Maven versions, once we get closer to an official Maven distribution

[fabriziodemaria]

I have little knowledge of jitpack, but my understanding is that we are going to generate aar libs to be attached to our draft releases here on GitHub. None of this is impacting the more "official" Maven publications.
As long as the above is correct, looks good to me 👍

[vahidlazio]

@fabriziodemaria true. btw, it's important to not mistake jitpack with the create release step. releases of the github is a different thing than jitpack. jitpack is just a tool that lets us depend on a jvm/android lib in github. basically they do all the local checkout and localMaven stuff internally.