fix(widget): bump @deepgram/ui to ^0.1.4 for dark-mode utility-var fix#57
Merged
Conversation
lukeocodes
pushed a commit
that referenced
this pull request
May 11, 2026
🤖 I have created a release *beep* *boop* --- ## [0.1.7](agents-widget-v0.1.6...agents-widget-v0.1.7) (2026-05-11) ### Bug Fixes * **widget:** bump @deepgram/ui to ^0.1.4 for dark-mode utility-var fix ([#57](#57)) ([2bc3118](2bc3118)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
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.
Summary
Picks up deepgram/ui#37 so the widget UMD ships with Tailwind v4 utility classes that actually follow
[data-dg-scheme="dark"]overrides.Why this needs a manual PR
The renovate.json on this repo sets
minimumReleaseAge: "11 days", so renovate would sit on@deepgram/ui@0.1.4until ~May 22 before proposing the bump. The 11-day soak is correct for third-party deps but the wrong shape for shipping our own fix end-to-end through the agent stack.The bug it unblocks downstream
@deepgram/uiships Tailwind v4 withprefix(dg), so utility classes like.dg:bg-cardreadvar(--dg-color-card). The@themeblock declares the public token as--color-card(Tailwind auto-pairs it to--dg-color-cardat root), but every dark-mode override block only touched the unprefixed namespace — so in dark mode the utilities kept resolving to the light-mode#f3f4f6(visible as near-white mic/speaker toggles and a blown-out textarea border inside the widget). 0.1.4 aliases every--dg-color-*tovar(--color-*)on[data-dg-agent], so dark-mode and external theme overrides on the public--color-*API propagate through to the utilities.Inside this PR, the rebuilt
dist/widget.umd.jsnow contains both--dg-color-card: #f3f4f6(the light-mode default Tailwind emits from@theme) and--dg-color-card: var(--color-card)scoped to[data-dg-agent], so consumers in dark mode get the dark card colour through the alias.Test plan
bun install— lockfile updated, no peer warningsbun run --filter '@deepgram/agents-widget' build— clean, UMD 390.83 KB (was 389.86 KB on CDN — alias block adds ~1 KB)bun run --filter '@deepgram/agents-widget' test— 29 pass / 0 fail--dg-color-card: var(--color-card)alias and dark-mode override on[data-dg-agent][data-dg-scheme="dark"]still sets--color-card: #222228(so utilities resolve through the alias to the dark value)Unblocks
@deepgram/agents-widget@0.1.7/widgets/latest/widget.umd.js