alpha in maven-metadata.xml <release>

[gabrieljones]

alpha and rc versions are showing up in the maven-metadata.xml <release> tag

https://repo1.maven.org/maven2/io/arrow-kt/arrow-core/maven-metadata.xml

Observed:

/metadata/versioning/release = 1.1.6-alpha.3

Expected:

/metadata/versioning/release = 1.1.5

[nomisRev]

Hey @gabrieljones,
We're releasing versions to Maven Central on every merge to main. So alpha and rc is the latest release to maven in those cases 🤔

[gabrieljones]

The alpha and rc versions should go into the <latest> tag, but not into the <release> tag.

[gabrieljones]

Hmm this may be a bug in Gradle itself.
https://github.com/gradle/gradle/blob/v7.6.0/subprojects/maven/src/main/java/org/gradle/api/publish/maven/internal/publisher/AbstractMavenPublisher.java#L101-L103

[raulraja]

Maven Central does not make a difference between releases, RC, and alphas. It just treats snapshots as non-releases. AFAIK everything else is considered a release. Another way to say this is we could have named those "jane", "joe" or whatever other identifier not as alpha, RC, etc. In practice, those are arrow releases too but in their name, they just include a hint for users as to what state we consider those stable.

As for correctly tagging in GitHub, maybe that is something we can control in the arrow build workflow or through the arrow-gradle-config library. /cc @JavierSegoviaCordoba

[gabrieljones]

The motivation of this issue is a desire to use the latest.release version range declaration like so:

build.gradle.kts

dependencies {
  implementation("io.arrow-kt:arrow-core:latest.release")
}

The expectation is this would pull in the latest stable version of arrow-core and exclude the alpha and rc versions.

Gradle also has latest.integration which is intended to include the latest alpha, rc, or SNAPSHOT version.