The library is published to Maven Central (project.scala: publish.organization com.halotukozak, cross-built JVM/Scala.js/Scala Native). Once 1.0.0 ships, patch/minor releases in the 1.x line should keep binary compatibility (per semver expectations for a published Scala library) — but nothing currently checks for that; a private[Regex]/private[CharSet] constructor tweak or an enum-case addition could silently break callers.
Add MiMa-equivalent binary-compatibility checking (via scala-cli, or a dedicated CI step) comparing each PR/release against the previous published version, wired into .github/workflows/ci.yml alongside the existing lint/test/compile jobs. Needs a first "baseline" tag once 1.0.0 itself ships.
The library is published to Maven Central (
project.scala:publish.organization com.halotukozak, cross-built JVM/Scala.js/Scala Native). Once 1.0.0 ships, patch/minor releases in the 1.x line should keep binary compatibility (per semver expectations for a published Scala library) — but nothing currently checks for that; aprivate[Regex]/private[CharSet]constructor tweak or an enum-case addition could silently break callers.Add MiMa-equivalent binary-compatibility checking (via scala-cli, or a dedicated CI step) comparing each PR/release against the previous published version, wired into
.github/workflows/ci.ymlalongside the existing lint/test/compile jobs. Needs a first "baseline" tag once 1.0.0 itself ships.