Resolve authored theme token overrides - #68
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
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.
Summary
ADM-13 Surface owner phase for canonical authored theme tokens from
@ankhorage/contracts.This PR:
@ankhorage/contracts@^7.2.0ThemeConfig.tokensoverrides into runtime spacing, radii, typography and shadow tokens@ankhorage/paradox@^0.1.21Token policy
spacing.noneandradii.noneremain zeroValidation
Dedicated ADM-13 refresh gate:
/home/runner/and/Users/Generated artifacts were then formatted with the repository's canonical Prettier configuration. Both temporary helper workflows removed themselves and are absent from the final diff.
Final normal PR CI on head
48868d3951e21bd69595c110c13186fb053a5febpasses frozen install, build, lint, format check, Knip, tests, typecheck and changeset validation.Release
Minor release:
@ankhorage/surface@2.2.0.Downstream ZORA/Studio work must wait for this Surface release; no downstream compatibility workaround belongs in this PR.