feat: show upload progress and skip re-uploads via checksum dedup#53
Merged
Conversation
This was referenced Jun 11, 2026
Merged
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.
What
Two upload UX improvements for
rb ffmpegwith local inputs:uploads.create(). The API already dedups on (org, checksum): re-running with the same input file skips the byte transfer entirely and reuses the existing ready asset — repeat uploads drop from seconds (or minutes for large files) to one ~300ms round trip.onProgresscallback into the step spinner. The Uploading line now showsfilename · 4.2 MB / 12.0 MB(and1/2prefixes for multiple inputs) instead of a mute timer. Single-PUT uploads report on completion; multipart uploads report per part.Tests
main-welcome.test.tsfailures on Windows dev machines are pre-existing (child-spawn ofbunPATH issue, passes in CI)Notes
Unrelated but found while testing:
package.jsonversionon main is1.0.0(manifest repair in #50 fixed.release-please-manifest.jsonbut notpackage.json), so built binaries self-report v1.0.0 and the update check misfires. Needs its own state-repair PR.