fix(react-ui): sync generated openui-defaults.scss with generator output - #804
Merged
Merged
Conversation
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
i-subham23
approved these changes
Jul 21, 2026
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
2 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.
What
Commits
packages/react-ui/src/openui-defaults.scssexactly asgenerate:css-utilscurrently produces it. The changes are cosmetic only — alpha formatting (0.1→0.10), line wrapping, and one blank line; every CSS value is identical.Why
react-ui's
preparescript runsbuild, whose first step regenerates this file on everypnpm install. The committed copy had drifted from the generator's output (the generator was updated in #787 without re-committing the file), so any fresh checkout — including the Publish NPM packages workflow — ends up with an unclean working tree, andpnpm publishfails its git check:That is what blocked the two react-ui 0.13.0 publish attempts today (runs 29833608212 and 29833815945). With this synced, install is idempotent again: the tree stays clean,
prettier --checkpasses on the regenerated content (verified — it also passed in the failed CI runs), and publish can proceed.Verification
Reproduced the CI environment (pnpm 9.15.4,
install --frozen-lockfile) on a pristine clone: before this change the tree dirties on install; with this file, regeneration is a no-op.