chore: version packages - #9
Merged
Merged
Conversation
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@sanring/cli@0.6.0
Minor Changes
205c89d:
initnow writessrc/sanring-theme.css— the full set of--sanring-*design tokens every component reads (color scales, semantic colors, radius, progress/badge tokens). Previously these variables only existed inside the docs app itself, so a freshsanring init+sanring addproduced components with no visible styling. Existing files are left alone by default (protects any brand-color edits); pass-f/--forceto reset to the shipped defaults. Also adds the--sanring-primary/--sanring-primary-fgalias needed for Radio and Checkbox's Tailwind-bridgedbg-primary/text-primary/border-primaryutilities to resolve.New
sanring diff [components...]command. Sanring UI has no version concept — components are copied source, not npm packages — so there was previously no way to know if a local file had drifted from the registry beforeadd --forceoverwrote it.diffcompares installed components andsanring-theme.cssagainst the current registry line by line, printing what's been customized locally versus what changed upstream. Omit component names to check everything currently installed.