chore(deps): bump @epam/ai-dial-ui-kit to 0.14.0-dev.37 - #33
Merged
Merged
Conversation
Pin the kit at 0.14.0-dev.37 in both `peerDependencies` and `devDependencies`, with the lockfile resolved to that exact build rather than to whatever the caret range picks up. No call-site changes are needed. The set of 0.14.0 migration guides is identical in dev.15 and dev.37, so nothing breaking landed in the window, and a selector diff of the shipped stylesheet removes nothing: the kit's colour and shadow tokens, and every `shadow-*` rule, are unchanged, so our hand-maintained mirror in `tailwind.config.js` stays in sync. The kit-side changes that could have reached us do not: - `Select`'s chosen option is now tinted instead of checked — we render no `Select`. - `Dropdown` gained `mark`/`rightControl` and dropped its `dropdownItem*ClassName` constants — we import none of them, and set neither `selectable` nor `checked` on any item. - `Tooltip` swapped its `innerWidth < 640` gate for `(hover: none)`, which restores tooltips in narrow embeds driven by a pointer. Our `useIsMobileScreen` drives layout only, never tooltip visibility, and `FileManagerTooltip` is mousemove-driven, so it was already absent on touch. - Control radii became themable via `rounded-control`. Every `rounded*` we write sits on a panel, a row or the grid container, never on a control, so none of them should follow `--radius-control`; the kit's own controls take the class from `@epam/ai-dial-ui-kit/styles.css`, which consumers import alongside ours. typecheck, lint, build and the 621 tests all pass against dev.37. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
PolinaGurinovich97
requested review from
stropalov and
valerydluski
as code owners
September 9, 2026 12:48
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.
What
Moves
@epam/ai-dial-ui-kitfrom0.14.0-dev.15to0.14.0-dev.37in bothpeerDependenciesanddevDependencies, with the lockfile resolved to that exact build.No call-site changes:
src/is untouched.Why nothing had to be adapted
The
0.14.0migration-guide set is identical in dev.15 and dev.37, so nothing breaking landed in the window. A full selector diff of the shippeddist/index.cssbetween the two builds removes 0 classes and adds 12; the--*token set is unchanged in both directions.The kit-side changes that could plausibly have reached us, and why they don't:
Select's chosen option is tinted instead of checkedSelectDropdowngainedmark/rightControl;dropdownItemSelectedClassName,…DisabledClassName,…DangerClassNamedropped from its constantsselectableorcheckedTooltipswapped itsinnerWidth < 640gate for(hover: none)— tooltips return in narrow pointer-driven embedsuseIsMobileScreendrives layout only, never tooltip visibility;FileManagerTooltipismousemove-driven, so it was already absent on touchrounded-control→--radius-control)rounded*we write sits on a panel, a row or the grid container, never on a control. The kit's own controls take the class from@epam/ai-dial-ui-kit/styles.css, which consumers import alongside ours (see README)shadowrules in the kit's stylesheet are byte-identical between the two builds, and ourshadowColors/boxShadowmirror intailwind.config.jsalready matches the kit's character for character.src/writes noshadow-*class at allgrid/file-manager/editorssubpath entries; root bundles renamedexports;Gridand friends are still exported from the root, and the subpath is documented as an ergonomic boundary rather than a tree-shaking requirementAlso new and unused here:
MenuItem/MenuItemMark,ThemeScope/useThemeScope,TextareaResize, the italic typography scale,registerAgGridModulesOnce.One note on
ThemeScope:FileManagerTooltipportals todocument.body, but the kit'sTooltipContentreads the scope through React context, which flows through portals — so a host-defined token scope still follows the bubble out. Nothing to wire up.Verification
npm run verify:agent-hook(typecheck + lint + tests) passes: 43 test files, 621 tests.npm run buildproduces both the bundle anddist/index.css.Unrelated pre-existing failure, not touched here:
npm run test:packagedies onspawnSync npm ENOENTbecausetools/package-smoke.mjsinvokesnpmwithoutshell: true, which never works on Windows. It fails the same way ondevelopment.🤖 Generated with Claude Code