Repository navigation
Version Packages - #637
Open
github-actions[bot] wants to merge 1 commit into
Open
Version Packages#637github-actions[bot] wants to merge 1 commit into
github-actions[bot] wants to merge 1 commit into
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
October 23, 2026 01:18
683afb4 to
f12f337
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 23, 2026 05:09
f12f337 to
7817f17
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
@tailor-platform/app-shell@1.19.0
Minor Changes
eb44189: AppShell components now use the typography roles. Titles, descriptions, captions, messages, error text, and key and value display render with
Text; controls such as buttons, inputs, menu items, badges, and table cells use the role classes. Most text looks the same. These values change:xsandsmAvatar initials.body-md-relaxed, 22.75 to 24px), attachment file names and upload text, the ActivityCard activity line, Appearance switcher options, and paragraphs inAlert.Description.Menu.GroupLabel(600 to 500).heading-sm(600).Alert.Titledrops its letter spacing (-0.025em to 0).code-sm, with an 18px line height.Element types do not change. Elements rendered with
Textand nodata-slotof their own getdata-slot="text".Patch Changes
aria-current="page"in custom, grouped, and generated navigation. Screen readers can identify the current page without application code editing the link element.Field.Controlnow logs a console warning when it is given an AppShell control that draws its own frame throughrender, such as<Field.Control render={<Select />} />. That composition renders a double border. The warning logs in every build, not only in development, because it only fires for UI that is already broken.Select,Combobox,Autocomplete,Checkbox,Textarea,DateField,DatePicker, andDateRangePickergo directly underField.Rootinstead. The Form, Select, and form-modal docs now say which controls go where.Use consistent IME detection, including the keyCode 229 fallback, in filters, cell editors, the command palette, and AI chat.
Textpasseschildrenonly when you give them. Arenderelement that supplies its own content now keeps it, for example<Text variant="label-md" render={<Field.Error />} />shows the validation message.Alert.RootandAlert.Description.Center items within each grid row while preserving the title, description, and action layout.