chore(ci): use published ancestor for stacked size baseline#14836
chore(ci): use published ancestor for stacked size baseline#14836LingyuCoder wants to merge 1 commit into
Conversation
Use the nearest ancestor that can publish binary-size data when a pull request is stacked on an unpublished branch, and explain the fallback in the comparison comment. Co-authored-by: ScriptedAlchemy <zackary.l.jackson@gmail.com>
📦 Binary Size-limit
🙈 Size remains the same at 66.59MB |
Rsdoctor Bundle Diff AnalysisFound 5 projects in monorepo, 5 projects with changes. 📊 Quick Summary
📋 Detailed Reports (Click to expand)📁 popular-libsPath:
📁 react-5kPath:
📁 react-1kPath:
📁 ui-componentsPath:
📁 react-10kPath:
Generated by Rsdoctor GitHub Action |
Merging this PR will degrade performance by 3.08%
|
| Mode | Benchmark | BASE |
HEAD |
Efficiency | |
|---|---|---|---|---|---|
| ❌ | Simulation | rust@create_chunk_assets |
1.4 ms | 1.5 ms | -3.13% |
| ❌ | Simulation | rust@create_chunk_hashes |
1.7 ms | 1.8 ms | -3.03% |
Tip
Investigate this regression by commenting @codspeedbot fix this regression on this PR, or directly use the CodSpeed MCP with your agent.
Comparing seal/binary-limit-stacked-base (95a0422) with main (25274d8)
Footnotes
-
47 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩
Summary
Related links
Checklist