Skip to content

chore(ui): define Tailwind CSS compatibility - #847

Merged
sean-brydon merged 1 commit into
mainfrom
codex/tailwind-compatibility-policy
Sep 7, 2026
Merged

sean-brydon merged 1 commit into
mainfrom
codex/tailwind-compatibility-policy

Conversation

@pasqualevitiello

@pasqualevitiello pasqualevitiello commented Sep 6, 2026 •

Copy link
Copy Markdown
Contributor

Summary

  • add Tailwind CSS as a peer dependency of @coss/ui
  • support Tailwind CSS versions >=4.1.17 <5

Why

coss components are compiled by the consuming application and already use features introduced in Tailwind CSS 4.1. Declaring the supported range allows package managers to surface incompatible Tailwind versions instead of letting unsupported utilities silently produce no CSS.

Testing

  • bunx biome check packages/ui/package.json
  • bun install --frozen-lockfile

@vercel

vercel Bot commented Sep 6, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
coss-com Ready Ready Preview Sep 6, 2026 9:57am UTC
coss-com-origin Ready Ready Preview Sep 6, 2026 9:57am UTC
coss-com-ui Ready Ready Preview Sep 6, 2026 9:57am UTC
coss-examples-calcom Ready Ready Preview Sep 6, 2026 9:57am UTC

Request Review

@sean-brydon
sean-brydon merged commit 3bab654 into main Sep 7, 2026
15 checks passed
@sean-brydon
sean-brydon deleted the codex/tailwind-compatibility-policy branch September 7, 2026 06:19
@linear-code

linear-code Bot commented Sep 7, 2026

Copy link
Copy Markdown

ENG-4181

This branch was successfully deployed

4 active deployments
Preview – coss-com-ui — db20e1c2 Deployed Sep 6, 2026 by vercel[bot]
Preview – coss-com-origin — db20e1c2 Deployed Sep 6, 2026 by vercel[bot]
Preview – coss-examples-calcom — db20e1c2 Deployed Sep 6, 2026 by vercel[bot]
Preview – coss-com — db20e1c2 Deployed Sep 6, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants