Skip to content

chore(deps): upgrade @datum-cloud/datum-ui to 3.4 - #524

Merged
mattdjenkinson merged 1 commit into
mainfrom
chore/datum-ui-3.4
Oct 1, 2026
Merged

mattdjenkinson merged 1 commit into
mainfrom
chore/datum-ui-3.4

Conversation

@mattdjenkinson

Copy link
Copy Markdown
Contributor

Summary

Upgrades @datum-cloud/datum-ui in ui/consumer from ^2.5.0 to ^3.4.0, crossing the 3.0.0 type-scale change.

ui/consumer is a Module Federation remote. At runtime the cloud-portal host supplies the shared datum-ui subpaths, and the host is already on datum-ui 3.x. So the plugin already renders against 3.x in the portal. This PR brings the local install (used for types, tests and standalone dev) up to the same version. The shared config in vite.config.ts is unchanged, and every shared subpath still resolves in 3.4.

Changes

  • @datum-cloud/datum-ui: ^2.5.0 → ^3.4.0 (resolves 3.4.0)
  • motion: ^12 → ^13 (resolves 13.4.6). datum-ui has declared motion >=13 <14 as a peer since 2.0.0, so the old ^12 was already out of range. The plugin doesn't import motion directly. Motion 13 only drops @emotion/is-prop-valid, which nothing here uses.
  • bun.lock refreshed. Only datum-ui and the motion family (motion, framer-motion, motion-dom, motion-utils) changed.

Migrations applied

Migration Files changed
text-2xs → text-5xs 0 (no usages)
text-1xs → text-2xs 0 (no usages)
Text / Paragraph size="base" → size="sm" 0 (the plugin doesn't use the Typography components)
Text / Title colour inheritance (textColor="default") 0 (no direct usages)
motion peer bump to 13 1 (package.json)

I searched all .ts/.tsx under src/, cn() strings and template literals. There are no .css files and no Tailwind config: the plugin uses the host's Tailwind build. I found no @tanstack/react-table usage (the 2.0 ColumnDef change) and no deprecated APIs from the 2.6 to 2.12 minors. No source changes were needed.

Visual check

The portal already renders these with 3.x, so nothing should change there. These are the places where 3.x behaves differently from 2.5, for a check in standalone dev and on tablet or mobile widths:

  • Network list (pages/network-list.tsx): the StatTiles values use text-3xl. Since 3.0, xl and larger shrink below 1024px. Also check the page title, empty state and table badges.
  • Network detail (pages/network-detail.tsx): the network name h1 uses text-2xl, so it also shrinks on tablet and mobile. Also check the resource section headings (text-lg, unchanged size) and the Topology popovers.
  • Cards across the detail tabs (Interfaces, Subnets, Services, Settings, Stats, CLI): since 2.9 Card no longer has a default drop shadow.
  • PageTitle / EmptyContent / Badge: internally they now inherit their parent's text colour instead of forcing foreground.

Test plan

  • bun install --frozen-lockfile (what the Dockerfile runs)
  • bun run typecheck (tsc --noEmit)
  • bun run lint (tsc --noEmit)
  • bun run test: 17 files, 196 tests pass
  • bun run build (vite build, the Docker build step)
  • Load the plugin in cloud-portal and check Network list and Network detail
  • Check Network list and detail at tablet (< 1024px) and mobile (< 768px) widths
  • Standalone bun run dev: check the screens above against the portal rendering

Bump @datum-cloud/datum-ui from ^2.5.0 to ^3.4.0 and motion from ^12 to ^13 to satisfy datum-ui's motion peer range (>=13 <14, required since 2.0.0). The cloud-portal host already supplies datum-ui 3.x for the shared subpaths, so this aligns the local install with what renders at runtime. No source changes are needed: the plugin uses none of the renamed type-scale classes or the Typography components.
@mattdjenkinson
mattdjenkinson requested a review from a team as a code owner October 1, 2026 10:30
@mattdjenkinson
mattdjenkinson merged commit 535b14c into main Oct 1, 2026
15 checks passed
@mattdjenkinson
mattdjenkinson deleted the chore/datum-ui-3.4 branch October 1, 2026 15:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants