feat(hosting frontend): file zipping - #7398
Merged
Merged
Conversation
Contributor
Pull request changelogAppAddedChangedDeprecatedRemovedFixedSecurityWebsiteAddedChangedDeprecatedRemovedFixedSecurityHostingAddedChangedDeprecatedRemovedFixedSecurity |
Contributor
Frontend previewsLast deployed commit is 655ec7dea741fe0105eed6a014fcd8ad5caaee8c Persistent
Latest commit
|
fetchfern
marked this pull request as ready for review
September 1, 2026 17:09
IMB11
approved these changes
Sep 1, 2026
|
Queued — the merge queue status continues in this comment ↓. |
Merge Queue Status
This pull request spent 7 minutes 33 seconds in the queue, including 6 minutes 30 seconds running CI. Required conditions to merge
|
10 tasks
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
2 participants
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.
/instead of the cwd.The new v1 zip route uses a json-seq response instead of publishing progress through the websocket like other operations in the v0 API. It's less consistent (at least while we still use the v0 files API) and has the disadvantage of cancelling the operation if the connection is aborted, although it's much simpler than the "job pattern".
Screen.Recording.2026-09-01.at.12.59.08.PM.mov