Server 1.215.3 fixes an edge case in remote cache artifact uploads. When a multipart upload completes, aborts, or expires before the client retries its finalization step, the service now treats the resulting NoSuchUpload response as a known conflict rather than an unhandled error. The CLI’s generated cache client also recognizes this case so it can prompt the client to start a fresh upload.
- Improved reliability of remote cache uploads when multipart sessions become stale before completion.
- Cache completion requests now return a typed 409 conflict instead of an unhandled server error.
- The CLI client has been regenerated to understand the stale upload conflict response.