- Shipped
- 7 ஆகஸ்ட், 2026 அன்று 7:17 AM UTC
- Author
- Kamo
- Commit
- 0e9417b
ESigService is CrashLooping for a reason that has nothing to do with e-signatures: it rebuilt against a shared library whose DepartmentService had grown a MailboxRepository constructor parameter, and this service does not scan com.kamo.z.shared.email, so the context could not start. The library now holds that repository as an ObjectProvider, and this rebuild is what picks the fix up. The build stages get the same treatment MediaService just needed to ship its own fix: Central through Google's byte-identical GCS mirror, five attempts on both stages instead of none on the shared-lib stage, and each attempt exiting 0 rather than breaking -- the old `&& break ||` left the loop on success and fell through on the final failure alike, so an unresolved tree could reach the package step and fail there instead.