Upgrade shadcn/ui and Tailwind CSS

Summary

We currently use shadcn (shadcn/ui) and Tailwind CSS in the frontend and should upgrade both to the latest stable releases (checked 2026-01-30).

Targets (as of 2026-01-30):

• shadcn/ui: 3.7.0

  • Changelog: https://ui.shadcn.com/docs/changelog
  • Releases: https://github.com/shadcn-ui/ui/releases
  • Update / migration guide & CLI docs: https://ui.shadcn.com/docs/cli
  • Community update notes/discussion: https://github.com/shadcn-ui/ui/discussions/7170

• Tailwind CSS: v4.1.18

  • Upgrade guide: https://tailwindcss.com/docs/upgrade-guide
  • Releases/Changelog: https://github.com/tailwindlabs/tailwindcss/releases
  • v4 announcement: https://tailwindcss.com/blog/tailwindcss-v4

Shadcn update notes

• shadcn copies component source into your project when you "add" them; updates are not automatic. Use the CLI to fetch the latest official component files, then manually merge if you have customizations.
• Example commands:
  • Update a single component (overwrites): npx shadcn@latest add <component> --overwrite
  • Update all components (use with extreme caution): npx shadcn@latest add --all --overwrite
• See the CLI docs and community discussion linked above for detailed merge guidance.

Migration and testing notes

• Backup customized components before running any overwrite commands.
• Run the frontend build and test suite after updating; smoke-test dialogs, forms, and the editor flows in a staging environment.
• For Tailwind, run the official upgrade tool and follow the Upgrade Guide; check PostCSS/Vite/plugin compatibility.

Request

Please verify compatibility with our build/tooling and prepare a PR that:

• Updates frontend package versions for shadcn/ui and tailwindcss
• Applies necessary code changes per migration guides (links above)
• Updates any related docs

Reported on: 2026-01-30T11:18:02.358Z

Labels: dependency, frontend

Start by reviewing the frontend package versions and the linked shadcn/ui and Tailwind CSS migration guides, then run the official Tailwind upgrade tool. Update the dependencies and apply any required migration changes, followed by the frontend build and test suite; done means compatibility is verified and dialogs, forms, and editor flows pass staging smoke tests.