chore: version packages#57
Merged
Merged
Conversation
e91fddc to
d662607
Compare
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
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
@tenphi/glaze@0.11.1
Patch Changes
#56
978bf60Thanks @tenphi! - Restructure documentation into focused README, API, methodology, and migration guides.#56
978bf60Thanks @tenphi! - Internal refactor: split the 2636-linesrc/glaze.tsinto focused, flatmodules (
config,hc-pair,shadow,warnings,scheme-mapping,validation,resolver,formatters,theme,palette,color-token) and dedupe a few parallel structures:runPass()+seedField()helper called four times.
tokens/tasty/cssexporters share abuildPaletteOutput()driver instead of duplicating theper-theme loop / prefix resolution / collision filtering /
primary-duplication logic.
init and
resetConfig(); both call a shareddefaultConfig().themeexports now cache the resolve result and invalidate it onany def mutation or
configure()/resetConfig()call (via anew
configVersioncounter), so back-to-back exports don'tre-run the four-pass resolver.
No public API or behavior changes.