Repository navigation
Promote develop prerequisites and Uppy 6 S3 uploads to master - #7302
Merged
Merged
Conversation
…-2026-11 fix(security): remediate community dependencies and request handlers
…loyment Prepare community-app develop deployment with OIDC v2.0.5
…v2.0.10 Use deployment scripts v2.0.10
…ndings fix: remediate community image scan findings
# Conflicts: # __tests__/shared/containers/tc-communities/JoinCommunity.jsx
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.
Promote the Uppy migration together with the existing develop prerequisites to master. The Uppy 6 build depends on the Node/build/dependency modernization already on develop; this PR therefore includes that broader promotion. It preserves master’s Topgear copy and community-test hotfixes.
Replace Filestack with Uppy 6.0 direct-to-S3 uploads. Submission pages retain a local ZIP input and drag/drop, show progress, support cancellation, and clear stale upload data on retry or replacement. Topgear URL submissions remain available.
The standalone files-api-v6 chooses the existing submission DMZ bucket and signs operations at
/v6/uploads/files. Both API environments are deployed. Submission creation, scanning and authorization continue through the existing Review API flow.UPLOADS_API_URLremains an optional override. Historical Filestack files are not migrated.Validation: current PR build, commit lint and security checks pass. The development container passed 179 test suites (529 tests), 153 snapshots, security checks, lint and its optimized build, and is deployed. Live API browser checks passed all seven purposes, 101 MiB multipart uploads, legacy downloads, multipart listing and cancellation. The three master-specific files previously passed 11 focused tests and lint.