fix(storage): content size from head when it can't be calculated

[designcode]

Note

Low Risk
Small, localized change to post-upload metadata calculation; main risk is an extra HEAD request and potential new error surface if it fails.

Overview
Fixes put() so returned size is no longer 0 when upload progress doesn’t provide total.

After a successful upload, if contentSize is still unknown, put() now calls head() on the uploaded object and uses ContentLength to populate the response.

^{Written by Cursor Bugbot for commit bcbd856. This will update automatically on new commits. Configure here.}

[greptile-apps]

Greptile Overview

Greptile Summary

• Updates put() to fallback to a head() request after upload when contentSize can’t be inferred from upload progress.
• This keeps the returned PutResponse.size more accurate for cases where the SDK doesn’t provide progress.total.
• Change is localized to packages/storage/src/lib/object/put.ts and uses existing head() helper with the same config/bucket resolution.

Confidence Score: 4/5

• Mostly safe to merge, but the size fallback path can mask HEAD failures and return an incorrect size without surfacing an error.
• Change is small and localized; main concern is the reachable success-path behavior when HEAD fails after upload and contentSize remains 0, which can mislead callers relying on PutResponse.size.
• packages/storage/src/lib/object/put.ts

Important Files Changed

Filename	Overview
packages/storage/src/lib/object/put.ts	Adds post-upload fallback to fetch object size via HEAD when contentSize couldn't be inferred from upload progress.

[greptile-apps]

_{1 file reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[github-actions]

🎉 This PR is included in version 2.12.2 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)

Your semantic-release bot 📦🚀