Repository navigation
Use standalone Files API for submission uploads - #7303
Merged
Merged
Conversation
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.
Point submission uploads at the standalone
files-api-v6service under/v6/uploads/files. Keep the optionalUPLOADS_API_URLoverride and the existing Review API submission creation/scan flow.Files API is deployed in dev and production. Existing saved file URLs remain supported through compatibility routing.
Validation: the development container passed security checks, lint, 179 test suites (529 tests), 153 snapshots, and the release build. Development API/browser checks passed for all seven upload purposes, including a 101 MiB multipart upload and legacy attachment URLs.
Current PR validation and security checks pass.