ci: make the bundle-size check informational, never fail - #307
Merged
Conversation
Bundle size is a guardrail, not a merge gate. Drop --strict from the compare step and remove the 'Fail on regression' step so the check always passes. The top severity tier renders 🟠 (was 🔴) and the comment says it never blocks merge. The script's --strict capability is kept for local/manual use; CI just doesn't pass it. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
filvecchiato
approved these changes
Aug 19, 2026
valentinfernandez1
approved these changes
Aug 19, 2026
📦 Bundle size impactComparing No size changes detected. 🟢 |
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
3 participants
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.
The bundle-size check has been failing PRs and it's become a problem, a size regression shouldn't block a merge, it should just tell us about it.
So this makes it purely informational. It still measures head vs base and posts the diff as a PR comment with per-entry severity, it just never fails the check anymore.