Release 0.31.1 — transformer-core + publish guardrail#186
Merged
Conversation
…OM_NAME Recurring pain: a new gradle module without its gradle.properties publishes wrong coordinates (artifactId defaults to the bare project name, not skainet-transformers-*) and/or fails at the Maven Central deploy (POM_NAME required) — discovered only at release/publish time. The bom-coverage plugin already iterates every published subproject (to build the BOM constraints), so add a configuration-time check there: each published module must set POM_ARTIFACT_ID + POM_NAME, else throw a clear GradleException naming the module + the fix. Now any build touching :llm-bom (i.e. CI) catches a forgotten gradle.properties immediately. Verified: passes with the file, fails with a precise message without it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
- VERSION_NAME 0.31.0 -> 0.31.1. - transformer-core/gradle.properties (POM_ARTIFACT_ID=skainet-transformers-transformer-core, POM_NAME) — makes it publishable; auto-covered by the BOM (verified in the BOM pom). - CHANGELOG [0.31.1]: transformer-core extraction (#183), additive, llm-core re-exports, all targets incl. androidNative; engine pin unchanged (ships against engine 0.31.0). - README: Current release -> 0.31.1, BOM example bump, project-structure row, What's new. - docs: getting-started-java + llama3-tool-calling BOM version bump; architecture module structure adds transformer-core. Engine-pin note: transformer-core needs nothing new from the engine (only skainet-lang-core, already in 0.31.0), so this patch intentionally relaxes the transformers-X.Y.Z <-> engine-X.Y.Z alignment — documented in the CHANGELOG. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 0.31.1 (against engine SKaiNET 0.31.0). Same flow as #181 (release/0.31.0 → develop); tag later.
What's in it
transformer-coreships (Extract transformer-core: NN primitives reusable on all targets incl. androidNative #183 / PR Extract transformer-core: NN primitives reusable on all targets (incl. androidNative) #185): the framework NN primitives now build on all targets incl.androidNative, re-exported byllm-core. Wired for publishing (transformer-core/gradle.properties→skainet-transformers-transformer-core) and auto-added to the BOM (verified in the generated pom).bom-coveragenow fails fast at configuration time when a published module ismissing
POM_ARTIFACT_ID/POM_NAME, instead of failing at the Maven Central deploy. This is therecurring "new module → forgotten gradle.properties → broken publish" issue, fixed for every future module.
[0.31.1]+ README (Current release / BOM example / module table / What's new) +docs (BOM-version bumps, architecture module structure).
Engine pin
Kept at
skainet = 0.31.0:transformer-coreneeds nothing new from the engine (onlyskainet-lang-core,already in 0.31.0). This patch intentionally relaxes the transformers-
X.Y.Z↔ engine-X.Y.Zalignment —documented in the CHANGELOG. (If strict alignment is preferred, cut engine 0.31.1 first and bump the pin.)
Naming heads-up
artifactId
skainet-transformers-transformer-core(matches the module). Change intransformer-core/gradle.propertiesbefore the first publish if a cleaner name is preferred — coordinatesare permanent once on Central.