- Shipped
- August 25, 2026 at 10:00 PM UTC
- Author
- Kamo
- Commit
- a927660
The library moved to 1.6.0 while every consumer stayed on 1.5.0. Consumer CI builds the library from a fresh clone into a cold ~/.m2 and ci-settings.xml mirrors Maven Central only, so 1.5.0 is fetchable from nowhere and the build fails to resolve it. It still passes locally, because 1.5.0 lingers in the developer's ~/.m2. No behaviour change: the version string sat at 1.5.0 across ~1,875 files of library commits, so a consumer pinning 1.5.0 was already compiling against current main. Only the coordinate moves.