Open icrc-fdeniger opened 3 weeks ago
Hello @santosh-pingle, @ktarasenko please tell me if this PR need to be modified. I understand that the version updates are the "tricky" part and will be happy to modify this. My point was to update them to the next version as GitHub Actions should produce SNAPSHOT of next versions.
Thanks
@icrc-fdeniger FYI the artifact version number changes introduced here will cause build failures once you rebase this after #2533 is merged. The required fix (after you have rebased it, not right now) is as simple as changing those version numbers also in the (new, TBD) docs/use/api.md
file; hopefully that's trivial. Please do shout if unclear!
@MJ1998 @santosh-pingle @ktarasenko merge this only after #2533.
@vorburger @santosh-pingle @ktarasenko should be ok now
@vorburger @santosh-pingle @ktarasenko should be ok now
LGTM! I say let's merge this... @santosh-pingle @ktarasenko @MJ1998 no objects, right?
Thanks for this PR @icrc-fdeniger. LGTM.
About the version proposal we would wanna keep the alpha/beta naming conventions. Reason - Using alpha and beta suffixes aligns with established conventions in semantic versioning and open-source software development. So we would like to stick with it.
Fixes #2503
Description Publish Maven artifacts in GitHub Packages
Type Feature
Checklist
Versions
common
module will be automatically deployed with the version0.1.0-alpha06-SNAPSHOT
in GitHub Packages and with0.1.0-alpha06
in the next release.Suggestion/question why not removeing beta/alpha as versions like 0.X.Y are considered as development version ?
if a dev Team wants to use an alpha/beta version it can use a dependency to a SNAPSHOT version ( the "unstable version created from the last build"). it's also possible to specify the artifact of a build with by example: engine-1.0.1-20240423.083712-3