Use presigned URLs for build artifact uploads - #57
Open
jpenilla wants to merge 5 commits into
Open
Conversation
kashike
self-requested a review
July 28, 2026 03:48
jpenilla
force-pushed
the
feat/presigned-uploads
branch
2 times, most recently
from
July 28, 2026 23:21
af6ef69 to
7902c9b
Compare
jpenilla
force-pushed
the
feat/presigned-uploads
branch
from
July 28, 2026 23:23
7902c9b to
2a8926a
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Add a new v3 publishing flow that uses presigned S3 upload URLs. Artifacts uploaded through this flow are staged in object storage, verified during publish, copied to their final content-addressed paths, and then cleaned up.
Unlike the legacy flow, the v3 flow does not rely on pod-local staging or Kubernetes pod routing. It also allows identical publish requests to be retried safely.
The new flow is available through
/v3/uploadand/v3/publish. The hidden, unprefixed legacy/uploadand/publishendpoints remain unchanged for existing clients. The companion PaperMC/fill-gradle#10 update migrates the Gradle plugin to the v3 flow.Before enabling the v3 publishing flow in production, an administrator must configure cleanup in the Cloudflare dashboard:
Expire abandoned Fill uploadsstaging/1 dayThe prefix restriction is important: the rule must only apply to
staging/, not the finalv1/objects/paths.