Repository navigation
perf(ci): Use pnpm pack for tarballs - #26024
Conversation
size-limit report 📦Compared: ee045cf (PR test merge using develop at 356d472) Against: 356d472 (develop) · base run #65426 ✅ Baseline matches: this diff contains only this PR's changes.
|
Optional E2E testsSome optional checks were not successful. They do not block the merge. 7 not successful, 50 successful. See the run.
Successful checks
|
|
drafting for now because there are some reservations and we might postpone this to v12 |
da14284 to
aeec453
Compare
@nicohrubec I don't think any of those changes are breaking, which one are we worried about and why? |
aeec453 to
403ca47
Compare
403ca47 to
7f4b207
Compare
0c46257 to
149122a
Compare
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
There are 2 total unresolved issues (including 1 from previous review).
❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.
Reviewed by Cursor Bugbot for commit 149122a. Configure here.
Co-Authored-By: OpenAI Codex <codex@openai.com>
Co-Authored-By: OpenAI Codex <codex@openai.com>
149122a to
ac2957a
Compare
Keep pnpm pack scripts alongside the consolidated circular dependency checks. Co-Authored-By: OpenAI Codex <codex@openai.com>

Why: Tarball preparation delays every E2E app. Switching from
npm packtopnpm packwith four workers made tarballs available to E2E jobs about two minutes earlier in our benchmark.Unsure about:
There are some minor changes to the packaged tarballs, but all of these probably don't matter iiuc or might even be improvements (e.g. including licenses in packages where they were missing atm). List of tarball changes courtesy of codex:
repositorychanges from a URL string to a{ type, url }object.build:tarballnow references pnpm.prepack; the build hook still runs before packing.