Current behavior
The Kinetic Merge project on Github has an entry in Scaladex here.
This refers to version 1.4.1, which was uploaded to Maven Central on 31st December 2024.
Since then there have been several releases:
1.5 - January 17th 2025
1.5.0 - January 18th 2025
1.5.1 - January 19th 2025
1.6.0 - February 28th 2025
It seems the entry on Scaladex is stuck on the outdated 1.4.1 version.
I looked at Americium, which also falls under the same organisation of com.sageserpent, and this is being correctly updated to the latest version.
Would somebody take a look, please?
Expected Behavior
Versions 1.5.0, 1.5.1 and 1.6.0 should appear.
Version 1.5 should probably appear, even though it is unwanted in this case.
Extra comments
If I can do something from my side, do let me know. I'm aware of the need to have an scm attribute in the POM on Maven Central, but this does exist, so I don't think the workaround of manually adding the entry to claims.json is applicable here, although if that's what it takes, I can try it.
One thing that does occur to me - just after the successfully indexed version 1.4.1, I mistakenly published version 1.5 of Kinetic Merge - this should have been version 1.5.0. I pushed out 1.5.0 the next day, but perhaps this has broken the indexing?
Search terms
Outdated, stale, version
Current behavior
The Kinetic Merge project on Github has an entry in Scaladex here.
This refers to version 1.4.1, which was uploaded to Maven Central on 31st December 2024.
Since then there have been several releases:
1.5 - January 17th 2025
1.5.0 - January 18th 2025
1.5.1 - January 19th 2025
1.6.0 - February 28th 2025
It seems the entry on Scaladex is stuck on the outdated 1.4.1 version.
I looked at Americium, which also falls under the same organisation of
com.sageserpent, and this is being correctly updated to the latest version.Would somebody take a look, please?
Expected Behavior
Versions 1.5.0, 1.5.1 and 1.6.0 should appear.
Version 1.5 should probably appear, even though it is unwanted in this case.
Extra comments
If I can do something from my side, do let me know. I'm aware of the need to have an
scmattribute in the POM on Maven Central, but this does exist, so I don't think the workaround of manually adding the entry toclaims.jsonis applicable here, although if that's what it takes, I can try it.One thing that does occur to me - just after the successfully indexed version 1.4.1, I mistakenly published version 1.5 of Kinetic Merge - this should have been version 1.5.0. I pushed out 1.5.0 the next day, but perhaps this has broken the indexing?
Search terms
Outdated, stale, version