- Shipped
- September 23, 2026 at 11:09 PM UTC
- Author
- Kamo
- Commit
- 4458e40
The library moved to 1.6.1 and this service still asked for 1.6.0. There is no window in which both resolve: the library is never published to a remote, so the only copy that can exist is the one each build compiles and installs, and a pin that does not match it fails outright with Could not find artifact **************** This service was green only for as long as its cached Docker layer held an old ~/.m2. The first push to invalidate that layer would have exposed a break that already existed, and blamed whatever commit happened to be next — which is exactly how it played out on computeservice, where three unrelated pushes took the blame before the cause was found. Two things hide this locally, so neither is evidence: a warm ~/.m2 still has the old version installed, and `COPY --from=... /root/.m2/repository` caches it in the image build.