Skip to content

chore(deps): bump tailwind-merge from 2.6.1 to 3.5.0 #11

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
dependabot wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore(deps): bump tailwind-merge from 2.6.1 to 3.5.0 #11

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,7 +45,7 @@
"recharts": "^2.12.2",
"redis": "^5.10.0",
"swr": "^2.2.5",
"tailwind-merge": "^2.2.1",
"tailwind-merge": "^3.5.0",
Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot Mar 5, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1: Incompatible major version bump: tailwind-merge v3 drops support for Tailwind CSS v3 and only supports Tailwind CSS v4+. This project uses tailwindcss: ^3.4.1 (in devDependencies), so upgrading tailwind-merge to v3 will silently break CSS class conflict resolution — the cn() utility in lib/utils/cn.ts will fail to properly merge Tailwind v3 classes.

Per the tailwind-merge v3.0.0 release notes: "This release drops support for Tailwind CSS v3 [...] you should upgrade to Tailwind CSS v4 and tailwind-merge v3 together."

Either keep tailwind-merge at ^2.6.1, or upgrade tailwindcss to v4 as well.

Prompt for AI agents 
Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 48:

<comment>**Incompatible major version bump**: `tailwind-merge` v3 drops support for Tailwind CSS v3 and only supports Tailwind CSS v4+. This project uses `tailwindcss: ^3.4.1` (in devDependencies), so upgrading tailwind-merge to v3 will silently break CSS class conflict resolution — the `cn()` utility in `lib/utils/cn.ts` will fail to properly merge Tailwind v3 classes.

Per the [tailwind-merge v3.0.0 release notes](https://newreleases.io/project/npm/tailwind-merge/release/3.0.0): *"This release drops support for Tailwind CSS v3 [...] you should upgrade to Tailwind CSS v4 and tailwind-merge v3 together."*

Either keep `tailwind-merge` at `^2.6.1`, or upgrade `tailwindcss` to v4 as well.</comment>

<file context>
@@ -45,7 +45,7 @@
     "redis": "^5.10.0",
     "swr": "^2.2.5",
-    "tailwind-merge": "^2.2.1",
+    "tailwind-merge": "^3.5.0",
     "uuid": "^13.0.0",
     "weave": "^0.11.0",
</file context>
Suggested change
"tailwind-merge": "^3.5.0",
"tailwind-merge": "^2.6.1",
Fix with Cubic

"uuid": "^13.0.0",
"weave": "^0.11.0",
"zod": "^3.25.76"
Expand Down
Loading