This server update fixes a bug that could prevent build artifacts from uploading when a project uses custom S3 storage and the upload is performed by someone outside that project’s account, such as a user uploading to an organization project.
The build upload start was being routed to the authenticated user’s account rather than the project’s account, causing the multipart upload to begin on the wrong storage backend. The subsequent upload steps and completion requests were then sent to the project’s storage, which rejected the upload because the upload ID belonged to a different backend. As a result, the build artifact never landed and server-side build processing never ran.
Build multipart uploads now consistently route through the project’s account, matching the generate URL and complete steps. This ensures build artifacts upload and process correctly regardless of who initiates the upload.