Update Versions - #73
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
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.
Changepacks
devup-mcp@0.10.0 → 0.10.1 - crates/devup-mcp/Cargo.toml
Patch
@devup-ui/reset-cssis a normalize rather than a preflight: for form controls it setsmargin: 0and-webkit-appearance: button, and that second rule preserves the native control appearance instead of removing it, so buttonpadding,borderandappearanceare deliberately untouched. That stays invisible until a button is sized in design units, becausebox-sizing: border-boxis global and an explicit8pxwidth cannot shrink below the6 + 6 + 2 + 2 = 16pxthat Chrome's defaultpadding: 1px 6pxandborder: 2px outsetalready occupy - an 8x8 button from a design renders 16x8, which is the reset behaving as specified rather than a defect, and the document now says so with the call-site fix. The second is alpha: a token is a CSS custom property, which the$token Scopesection already establishes, so a token at partial opacity iscolor-mix()overvar(--token)and needs neither an alpha token nor a hardcoded copy of the colour. Without that, a screen hardcoded#F7F3EC66beside a$bgof the same value, which is not merely redundant but wrong under theming -$bgfollows the active theme and the literal does not, so the surface stays light in dark mode. This matters here because devup-mcp vendors the document into the binary, sodevup_skills installwrites it on machines with no network, which are the machines least able to work either answer out for themselves.