chore: correct the macOS bundle size to ~1.6 GB, bump to 0.5.15 - #253
Merged
Conversation
added 2 commits
August 6, 2026 19:11
The per-chip bundles (#252) were sized from an estimate made before they existed. They have now been built and verified — CLOSURE CLEAN, zip -t, sha256sum -c on both — and the real figures are 1637 MB arm64 and 1669 MB x86_64, so APPROX_BUNDLE_MB drops 1700 -> 1600. The prose that quotes a size does so to justify a decision — what fetching the wrong chip's bundle actually costs — so those numbers move with it rather than being dropped: 1.7 -> 1.6, and the Rosetta test's "3.4 GB to land 1.7" -> "3.2 GB to land 1.6". Matching updates in codev-scripts and codev-landing-page.
The reason to require --arch is that nothing on a non-Mac host implies which Mac the bundle is for; the download size was supporting colour, and the README now carries no hardcoded bundle size at all.
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
1 participant
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.
Why
The per-chip bundles (#252) were sized from an estimate made before they existed. They have since been built and verified, and the real figures are:
codev-office-macos-arm64.zipcodev-office-macos-x86_64.zipDown from 3.04 GB for every Mac — about 47% less to download.
Changes
APPROX_BUNDLE_MB: macOS targets 1700 → 1600.1.7 → 1.6in the Rosetta comment, the--archrefusal comment, and the README. The Rosetta test's "3.4 GB to land 1.7" becomes "3.2 GB to land 1.6".Note
APPROX_BUNDLE_MBis the pre-download heads-up only — real progress totals still come from the server's content-length, so the ~2% it now understates the x86_64 bundle by never reaches the progress bar.How the bundles were verified
check-closure.py→CLOSURE CLEAN (4 bundles);unzip -tOK on both;sha256sum -c101/101 and 103/103; zero cross-arch wheels in eitherpython-wheels/; each bundle's Chromium carries only its own chip.Checks
pnpm typecheck,pnpm check,pnpm test— 1405 passed, 2 skipped. The pre-commit hook ran the same gate plusbuild.Companions
Still outstanding
The bundles are not uploaded yet. Until both zips are in
codev-storage/codev-office/, a release carrying #252 hands every Mac a 404. Merging is safe in any order; publishing is not.🤖 Generated with Claude Code