Repository navigation
🚀 Promote develop → main - #27
Merged
Merged
Conversation
…ys rendered 0.7.0 completed the ladder and set `radius-xl` through `radius-4xl` to `0rem` on this brand, reasoning that a brand flat at radius/sm/md/lg is flat all the way down. The reasoning was sound and the premise was wrong: those steps had never rendered flat. The contract did not define them, so they fell through to Tailwind's defaults, and every component built on this brand has been designed against those values for as long as the brand has existed. Zeroing them squared 24 corners on maxhealth.tech (product cards, the countdown page) and every chat bubble in AIHR. Both read as broken rather than as flat, which is the signal that the tail was never the accident — the missing declaration was. So the ladder is now the design, written down: flat at the sizes that trim a CONTROL (button, input, badge, table cell — everything through `lg`, all still `0rem`), soft at the sizes that shape a SURFACE, where the step draws a card or a bubble rather than an edge of one. Values are Tailwind's, so no consumer needs an edit to get back what it had before 0.7.0. `dashboard` is untouched. Also merges main's release commit, which develop was behind — without it this PR's CHANGELOG would have reverted 0.7.0 back out of its released section. Verified: npm run check (tsc, build, 38 tests).
feat(maxhealth): a real radius ladder above lg, which is what it always rendered
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.
Standing promotion PR, kept up to date by
auto-pr.yml.Merging this publishes
brandcto the public npm registry.release.ymlruns onpush to
mainand ships whateverpackage.jsonsays, so bump the version in the PRthat adds the change rather than here. A merge whose version is already published
publishes nothing and says so in the run summary, which keeps a docs- or CI-only
merge green.