Published BOM 0.21.1 imports unresolvable `sk.ainet:skainet-bom:0.21.0`

[michalharakal]

Summary

The BOM published as sk.ainet.transformers:skainet-transformers-bom:0.21.1 cannot be consumed from public Maven Central. Any project that does

implementation(platform("sk.ainet.transformers:skainet-transformers-bom:0.21.1"))

fails dependency resolution because the BOM transitively imports an artifact that has never been published.

Evidence

The POM at https://repo.maven.apache.org/maven2/sk/ainet/transformers/skainet-transformers-bom/0.21.1/skainet-transformers-bom-0.21.1.pom ends with this <dependencyManagement> entry:

<dependency>
  <groupId>sk.ainet</groupId>
  <artifactId>skainet-bom</artifactId>
  <version>0.21.0</version>
  <type>pom</type>
  <scope>import</scope>
</dependency>

But there is no sk.ainet:skainet-bom on Central at all — the directory https://repo.maven.apache.org/maven2/sk/ainet/skainet-bom/ 404s, and there is no maven-metadata.xml. The engine BOM has simply never been published. Tracked in the engine repo: SKaiNET-developers/SKaiNET#584.

Reproduction

// settings.gradle.kts → mavenCentral() only
dependencies {
    implementation(platform("sk.ainet.transformers:skainet-transformers-bom:0.21.1"))
    implementation("sk.ainet.transformers:skainet-transformers-inference-bert")
}

Gradle reports:

Could not resolve sk.ainet.transformers:skainet-transformers-bom:0.21.1.
  > Could not parse POM ...skainet-transformers-bom-0.21.1.pom
    > Could not find sk.ainet:skainet-bom:0.21.0.

Workaround for consumers

Stop importing the BOM. Pin every transformer artifact at 0.21.1 directly and every sk.ainet.core:* artifact at 0.21.0 (which is what the individual transformer POMs already pin internally). This works against public Maven Central with no extra repositories.

Suggested fix (one of)

1. Best: have the engine repo publish sk.ainet:skainet-bom (Publish sk.ainet:skainet-bom to Maven Central SKaiNET#584) and bump the import here to a real version (likely 0.22.x once the engine catches up).
2. Alternative: drop the <scope>import</scope> of the engine BOM from the transformers BOM and instead enumerate the engine artifacts (sk.ainet.core:skainet-lang-core, skainet-backend-cpu, skainet-io-core, skainet-io-safetensors, skainet-compile-core) at the engine version transformers was built against.
3. Quickest: republish a 0.21.2 patch where the import points at a version that actually exists.

Why this matters

This is the only published BOM, so any downstream that follows the standard "import the BOM, then add artifacts without versions" pattern is hard-blocked. Hit while migrating the leaf-cli sample to 0.21.1.

Related

• Engine-side issue (BOM publishing): Publish sk.ainet:skainet-bom to Maven Central SKaiNET#584
• Off-by-one: gradle.properties says VERSION_NAME=0.21.1 but the BOM imports skainet-bom:0.21.0, suggesting the publish was cut from a state pinning the prior engine BOM.

[michalharakal]

Update from the engine side: sk.ainet:skainet-bom:0.22.2 is now published (SKaiNET-developers/SKaiNET#584 closed). The new BOM lists all 16 engine modules at 0.22.2.

0.21.0 of the engine BOM was not backfilled, so this issue is still live — the published skainet-transformers-bom:0.21.1 POM still tries to import sk.ainet:skainet-bom:0.21.0 which doesn't exist, and so the transformers BOM is still unresolvable from mavenCentral().

Path forward (replaces the previous "Suggested fix" list):

1. Cut a transformers release (0.22.0 aligned with the engine, or a 0.21.2 patch) whose BOM imports sk.ainet:skainet-bom:0.22.2 instead of 0.21.0.
2. While at it, bump every sk.ainet.core:* pin in the individual transformer POMs from 0.21.0 to 0.22.2 so consumers don't need a Gradle-side force to skip the dead 0.21.0 line.

Verification once published:

dependencyResolutionManagement {
    repositories { mavenCentral() }
}
dependencies {
    implementation(platform("sk.ainet.transformers:skainet-transformers-bom:<new>"))
    implementation("sk.ainet.transformers:skainet-transformers-inference-bert")
}

Should resolve with no Could not resolve and pull engine 0.22.2 artifacts.

Downstream tracking the migration: michalharakal/SKaiNET-leaf-cli, currently pinned at transformers:0.21.1 + core:0.21.0 and bypassing the BOM. As an interim step it can already switch the engine pins to platform("sk.ainet:skainet-bom:0.22.2") to get the new engine line; the only thing it can't do yet is consume the transformers BOM.

[michalharakal]

Engine baseline has moved on again: sk.ainet:skainet-bom:0.23.0 is now published (alongside all sk.ainet.core:*:0.23.0 artifacts). Previous comment referenced 0.22.2; the cleaner target for the transformers BOM fix is now 0.23.0.

Updated reproducer (still fails, since this issue is the published transformers BOM itself):

dependencyResolutionManagement { repositories { mavenCentral() } }
dependencies {
    implementation(platform("sk.ainet.transformers:skainet-transformers-bom:0.21.1"))
    implementation("sk.ainet.transformers:skainet-transformers-inference-bert")
}
// > Could not find sk.ainet:skainet-bom:0.21.0.

Suggested fix unchanged in shape — cut a transformers release whose BOM imports sk.ainet:skainet-bom:0.23.0 instead of 0.21.0, and bump engine pins in the individual transformer POMs from 0.21.0 to 0.23.0.

Note: engine 0.23.0 BOM has a small completeness gap — skainet-compile-opt is not listed in <dependencyManagement> and so transitive 0.21.0 doesn't get upgraded by the BOM. Tracked as SKaiNET-developers/SKaiNET#592 and orthogonal to this issue, but worth aligning on so the next transformers release pins clean engine versions.

Downstream michalharakal/SKaiNET-leaf-cli is now consuming sk.ainet:skainet-bom:0.23.0 for the engine line; transformers still pinned at 0.21.1 directly until this lands.