Skip to content

chore: refresh size-gate baselines#4119

Open
sxlijin wants to merge 1 commit into
canaryfrom
chore/size-gate-baseline-refresh
Open

chore: refresh size-gate baselines#4119
sxlijin wants to merge 1 commit into
canaryfrom
chore/size-gate-baseline-refresh

Conversation

@sxlijin

@sxlijin sxlijin commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Adopted from CI run 6951c866434f7ab480162b38483a2d54a76c6529.

Binary size checks passed

7 passed

Artifact Platform File Gzip Gated on Baseline Delta Status
baml-cli Linux 🔒 25.6 MB 10.8 MB file 25.3 MB +275.0 KB (+1.1%) OK
packed-program Linux 🔒 17.2 MB 7.1 MB file 17.0 MB +153.1 KB (+0.9%) OK
baml-cli macOS 🔒 19.8 MB 9.4 MB file 19.6 MB +231.5 KB (+1.2%) OK
packed-program macOS 🔒 13.4 MB 6.2 MB file 13.2 MB +198.3 KB (+1.5%) OK
bridge_wasm WASM 16.3 MB 🔒 4.4 MB gzip 4.4 MB +19.2 KB (+0.4%) OK
baml-cli Windows 🔒 21.3 MB 9.7 MB file 21.1 MB +230.9 KB (+1.1%) OK
packed-program Windows 🔒 14.3 MB 6.3 MB file 14.2 MB +150.5 KB (+1.1%) OK

🔒 = the size this artifact is GATED on (ceiling + delta). Binaries gate on file size (installed binary); WASM gates on gzip (download size). The other size is shown for information only.


Generated by cargo size-gate

Summary by CodeRabbit

  • Chores
    • Updated build artifact size thresholds across macOS, Linux, Windows, and WebAssembly targets.
    • Refreshed recorded artifact size metrics and build metadata for supported platforms.
    • Helps ensure size checks reflect current release artifact sizes.

@vercel

vercel Bot commented Jul 22, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
beps Ready Ready Preview, Comment Jul 22, 2026 10:29am
promptfiddle Ready Ready Preview, Comment Jul 22, 2026 10:29am
promptfiddle2 Ready Ready Preview, Comment Jul 22, 2026 10:29am

Request Review

@coderabbitai

coderabbitai Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

📝 Walkthrough

Walkthrough

Updated size-gate ceilings and refreshed recorded artifact size metadata for baml-cli, packed-program, and bridge_wasm across supported platforms.

Changes

Size-gate baseline refresh

Layer / File(s) Summary
Update artifact size ceilings
baml_language/.cargo/size-gate.toml
Increased platform-specific baml-cli and packed-program file limits, plus the bridge_wasm gzip limit.
Refresh recorded artifact baselines
baml_language/.ci/size-gate/*.toml
Updated build timestamps, commit identifiers, and recorded artifact byte metrics for macOS, Linux, Windows, and wasm32 builds.

Estimated code review effort: 1 (Trivial) | ~5 minutes

Possibly related PRs

Suggested reviewers: 2kai2kai2, codeshaunted, hellovai

Poem

I’m a rabbit with a byte-sized tune,
Updating limits beneath the moon.
CLI and WASM hop in line,
Fresh build numbers now shine.
Packed programs bounce along—
Size gates sing their measured song.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the main change: refreshing size-gate baselines across platforms.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/size-gate-baseline-refresh

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

Copy link
Copy Markdown

⏭️ Performance benchmarks were skipped

Perf benchmarks (CodSpeed) are opt-in on pull requests — they no longer run on every push. They always run automatically after merge to canary/main.

To run them on this PR, do any of the following, then push a commit (or re-run CI):

  • Add RUN_CODSPEED=1 to the PR description, or
  • Include run-perf or /perf in the PR title or any commit message.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 2

🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@baml_language/.cargo/size-gate.toml`:
- Line 50: Update or remove the explanatory baseline comments near
max_file_bytes and the corresponding entries around lines 61–67 so they match
the current recorded measurements, including Linux’s 25,560,272-byte baseline.
Leave the configured ceilings unchanged.
- Around line 49-52: Remove the duplicate TOML table declarations in the
size-gate configuration, including the repeated artifacts.baml-cli platform
headers around the affected entries. Keep one header per platform and preserve
each platform’s existing max_file_bytes ceiling so the configuration parses
successfully.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: c3f30fe1-e848-47f2-ac59-b747b42d4e6a

📥 Commits

Reviewing files that changed from the base of the PR and between 6951c86 and 04036de.

📒 Files selected for processing (5)
  • baml_language/.cargo/size-gate.toml
  • baml_language/.ci/size-gate/aarch64-apple-darwin.toml
  • baml_language/.ci/size-gate/wasm32-unknown-unknown.toml
  • baml_language/.ci/size-gate/x86_64-pc-windows-msvc.toml
  • baml_language/.ci/size-gate/x86_64-unknown-linux-gnu.toml

Comment on lines 49 to 52
[artifacts.baml-cli.platform.x86_64-unknown-linux-gnu]
max_file_bytes = 26_043_822
max_file_bytes = 26_327_081
# Windows x86_64: baseline 21.08 MB file (21_075_968), ceiling = baseline x1.03.
[artifacts.baml-cli.platform.x86_64-pc-windows-msvc]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🎯 Functional Correctness | 🔴 Critical | ⚡ Quick win

Remove the duplicate TOML table headers.

The repeated table declarations at Lines 49, 52, 55, 60, 63, and 66 make this configuration invalid for TOML parsers, preventing the size-gate tool from loading the ceilings.

Proposed fix
 [artifacts.baml-cli.platform.x86_64-unknown-linux-gnu]
-[artifacts.baml-cli.platform.x86_64-unknown-linux-gnu]

 [artifacts.baml-cli.platform.x86_64-pc-windows-msvc]
-[artifacts.baml-cli.platform.x86_64-pc-windows-msvc]

 [artifacts.packed-program]
-[artifacts.packed-program]

 [artifacts.packed-program.platform.aarch64-apple-darwin]
-[artifacts.packed-program.platform.aarch64-apple-darwin]

 [artifacts.packed-program.platform.x86_64-unknown-linux-gnu]
-[artifacts.packed-program.platform.x86_64-unknown-linux-gnu]

 [artifacts.packed-program.platform.x86_64-pc-windows-msvc]
-[artifacts.packed-program.platform.x86_64-pc-windows-msvc]

Also applies to: 55-67

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@baml_language/.cargo/size-gate.toml` around lines 49 - 52, Remove the
duplicate TOML table declarations in the size-gate configuration, including the
repeated artifacts.baml-cli platform headers around the affected entries. Keep
one header per platform and preserve each platform’s existing max_file_bytes
ceiling so the configuration parses successfully.

# Linux x86_64: baseline 25.27 MB file (25_272_400), ceiling = baseline x1.03.
[artifacts.baml-cli.platform.x86_64-unknown-linux-gnu]
max_file_bytes = 26_043_822
max_file_bytes = 26_327_081

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win

Synchronize the explanatory baseline comments.

The ceilings now correspond to newer measurements, but nearby comments still cite old values—for example, Linux 25,272,400 versus the recorded 25,560,272 bytes. Update or remove these comments to avoid misleading future refreshes.

Also applies to: 61-67

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@baml_language/.cargo/size-gate.toml` at line 50, Update or remove the
explanatory baseline comments near max_file_bytes and the corresponding entries
around lines 61–67 so they match the current recorded measurements, including
Linux’s 25,560,272-byte baseline. Leave the configured ceilings unchanged.

@github-actions

Copy link
Copy Markdown

Binary size checks passed

7 passed

Artifact Platform File Gzip Gated on Baseline Delta Status
baml-cli Linux 🔒 25.6 MB 10.8 MB file 25.6 MB +0 B (+0.0%) OK
packed-program Linux 🔒 17.2 MB 7.1 MB file 17.2 MB +0 B (+0.0%) OK
baml-cli macOS 🔒 19.8 MB 9.4 MB file 19.8 MB +0 B (+0.0%) OK
packed-program macOS 🔒 13.4 MB 6.2 MB file 13.4 MB +0 B (+0.0%) OK
baml-cli Windows 🔒 21.3 MB 9.7 MB file 21.3 MB +0 B (+0.0%) OK
packed-program Windows 🔒 14.3 MB 6.3 MB file 14.3 MB +0 B (+0.0%) OK
bridge_wasm WASM 16.3 MB 🔒 4.4 MB gzip 4.4 MB +0 B (+0.0%) OK

🔒 = the size this artifact is GATED on (ceiling + delta). Binaries gate on file size (installed binary); WASM gates on gzip (download size). The other size is shown for information only.


Generated by cargo size-gate · workflow run

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant