- Shipped
- August 7, 2026 at 7:08 AM UTC
- Author
- Kamo
- Commit
- c0d42d8
The startup fix could not ship: the build died resolving byte-buddy with "Tag mismatch", which reads like a missing artifact but is a download corrupted mid-transfer over this runner's link. Nothing about it is specific to that jar — DocsService lost hibernate-core and SecurityService lost bcprov the same way. Central is also rate-limited, and the multi-stage build starts from a cold ~/.m2 every run, so concurrent service builds draw HTTP 429s. Both stages now resolve through Google's byte-identical GCS mirror and retry five times before giving up; the shared-lib stage had no retry at all, so a single corrupt transfer was fatal. Each attempt exits 0 on success rather than breaking, so a final failure cannot carry an unresolved dependency tree into the next stage.