Skip to content

chore: refresh C# package size policy - #4454

Merged
sxlijin merged 1 commit into
canaryfrom
agent/refresh-csharp-size-policy
Aug 16, 2026
Merged

sxlijin merged 1 commit into
canaryfrom
agent/refresh-csharp-size-policy

Conversation

@sxlijin

@sxlijin sxlijin commented Aug 16, 2026 •

Copy link
Copy Markdown
Contributor

What changed

  • Refresh all eight C# native asset baselines from the exact artifacts produced by release run 31925845745 at source 4b08255ca0142419bf500d3007c1b84b86242cdc.
  • Update the reviewed evidence to the reproduced 75,118,828-byte deterministic NuGet package.
  • Keep the compressed-package regression baseline and 200 MB registry safety ceiling unchanged.

Why

The 0.17.0 release verification failed because every native target had grown slightly beyond the stale July baseline plus its 10% budget. The first reported failure was Apple ARM64: 23,777,024 bytes against a 23,495,683-byte ceiling. Publishing remained blocked behind the all-builds gate.

Failed run: https://github.com/BoundaryML/baml/actions/runs/31925845745

Validation

  • Reproduced package assembly locally from all eight provenance-bound artifacts from run 31925845745.
  • Both normalized NuGet builds produced SHA-256 c37be3d9257070bb19034c5262f9a9ec30d9c5e05dbbb0a1ec1145e366e8d3ee.
  • Package size is 75,118,828 bytes, below the unchanged 80,500,000-byte regression ceiling.
  • python3 scripts/tests/test_release_pipeline_contract.py (26 passed)
  • jq empty release/csharp-package-size-policy.json
  • git diff --check

Summary by CodeRabbit

  • Chores
    • Updated package size evidence with the latest workflow run, source commit, and measurement date.
    • Refreshed compressed native payload size measurements and platform-specific baselines across all supported targets.

@vercel

vercel Bot commented Aug 16, 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 Aug 16, 2026 4:48am
promptfiddle2 Ready Ready Preview Aug 16, 2026 4:48am

Request Review

@coderabbitai

coderabbitai Bot commented Aug 16, 2026 •

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a525ead1-e0bb-40ac-9ee5-4e16c70642f8

📥 Commits

Reviewing files that changed from the base of the PR and between 4b08255 and 54aa73c.

📒 Files selected for processing (1)
  • release/csharp-package-size-policy.json

Included review availability: Your plan includes up to 8 reviews per rolling hour; 7 remain after this review.


📝 Walkthrough

Walkthrough

The C# package size policy now records newer measurement evidence and larger compressed native payload baselines for all eight target platforms.

Changes

C# package size policy

Layer / File(s) Summary
Refresh size evidence and baselines
release/csharp-package-size-policy.json
The policy now records a newer workflow run, source commit, measurement date, compressed native payload size, and per-platform native asset byte counts.

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

Merge Risk: ⚪ Minimal · up to 54aa7

This refreshes package-size baselines while keeping the regression ceiling unchanged; the reported validation passes, and no actionable merge-blocking risk remains after normal checks and review.

Possibly related PRs

Poem

A rabbit checks the numbers twice,
New size records sparkle nice.
Eight platforms hop in line,
With fresh baselines, neat and fine.
“Package policy,” cheers the hare!

🚥 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 and concisely describes the package size policy refresh, which is the main change in the pull request.
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 agent/refresh-csharp-size-policy

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.

@sxlijin
sxlijin marked this pull request as ready for review August 16, 2026 04:41
@vercel
vercel Bot temporarily deployed to Preview – beps August 16, 2026 04:41 Inactive
@vercel
vercel Bot temporarily deployed to Preview – promptfiddle2 August 16, 2026 04:48 Inactive
@sxlijin
sxlijin added this pull request to the merge queue Aug 16, 2026
Merged via the queue into canary with commit 36545fd Aug 16, 2026
37 checks passed
@sxlijin
sxlijin deleted the agent/refresh-csharp-size-policy branch August 16, 2026 04:50

This branch was previously deployed

2 inactive deployments
Preview – promptfiddle2 — 54aa73cb Deployed Aug 16, 2026 by vercel[bot]
Preview – beps — 54aa73cb Deployed Aug 16, 2026 by vercel[bot]
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