fix(deps): update dependency tailwind-merge to v3

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
tailwind-merge	^2.2.2 -> ^3.0.0

---

Release Notes

dcastil/tailwind-merge (tailwind-merge)

v3.4.0

Compare Source

v3.3.1

Compare Source

Bug Fixes

• Fix arbitrary value using color-mix() not being detected as color by @​dcastil in #​591

Full Changelog: dcastil/tailwind-merge@v3.3.0...v3.3.1

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, @​sourcegraph, a private sponsor, @​block and @​shawt3000 for sponsoring tailwind-merge! ❤️

v3.3.0

Compare Source

New Features

• Add support for tailwind CSS v4.1.5 by @​dcastil in #​575

Full Changelog: dcastil/tailwind-merge@v3.2.0...v3.3.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, @​sourcegraph, a private sponsor and @​block for sponsoring tailwind-merge! ❤️

v3.2.0

Compare Source

New Features

• Add support for Tailwind CSS v4.1 by @​dcastil in #​565

Full Changelog: dcastil/tailwind-merge@v3.1.0...v3.2.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, @​sourcegraph and a private sponsor for sponsoring tailwind-merge! ❤️

v3.1.0

Compare Source

New Features

• Add support for Tailwind CSS v4.0.10 by @​dcastil in #​546

Bug Fixes

• Fix length variable in via-(length:*) class being merged with via-<color> classes accidentally by @​dcastil in #​559

Documentation

• Fix typo in comment in types.ts by @​roottool in #​549
• Update shadow scale recipe to tailwind merge v3 API by @​dcastil in #​545

Other

• Fix metrics report action erroring on PRs from forks by @​dcastil in #​551

Full Changelog: dcastil/tailwind-merge@v3.0.2...v3.1.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, @​sourcegraph and a private sponsor for sponsoring tailwind-merge! ❤️

v3.0.2

Compare Source

Bug Fixes

• Fix px value not being recognized for some class groups by @​dcastil in #​538
• Fix doc comment being in incorrect place in default config by @​gjtorikian in #​526

Full Changelog: dcastil/tailwind-merge@v3.0.1...v3.0.2

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, @​sourcegraph and a private sponsor for sponsoring tailwind-merge! ❤️

v3.0.1

Compare Source

Bug Fixes

• Update info about supported Tailwind CSS version in README by @​dcastil in b9c136d
• Update incorrect link in v3 changelog by @​dcastil in e22885e

Full Changelog: dcastil/tailwind-merge@v3.0.0...v3.0.1

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, @​sourcegraph and a private sponsor for sponsoring tailwind-merge! ❤️

v3.0.0

Compare Source

Tailwind CSS v4 is here and it's time to upgrade tailwind-merge to support it. tailwind-merge v3.0.0 is more accurate than ever and follows the Tailwind CSS spec more closely than in v2. That is thanks to Tailwind CSS v4 being more consistent than ever.

This release drops support for Tailwind CSS v3 and in turn adds support for Tailwind CSS v4. That means you should upgrade to Tailwind CSS v4 and tailwind-merge v3 together. All breaking changes are related to the Tailwind CSS v4 support.

Check out the migration guide and if you have any questions, feel free to create an issue.

Breaking Changes

• Dropping support for Tailwind CSS v3 in favor of support for Tailwind CSS v4 by @​dcastil in #​518
• Theme scales keys changed and now match Tailwind CSS v4 theme variable namespace exactly by @​dcastil in #​518
• isLength validator was removed and split into separate validators isNumber and isFraction by @​dcastil in #​518
• Prefix defined in config shouldn't include combining - character anymore by @​dcastil in #​518
• Tailwind CSS v3 prefix position in class not supported anymore in favor of Tailwind CSS v4 position by @​dcastil in #​518
• Custom separators are no longer supported by @​dcastil in #​518
• New mandatory orderSensitiveModifiers property in config when using createTailwindMerge by @​dcastil in #​518
• DefaultThemeGroupIds type union consists of different string literals than before by @​dcastil in #​518
• Classes removed in Tailwind CSS v4 are not supported by tailwind-merge anymore by @​dcastil in #​518

New Features

• Support for new important modifier position at the end of class by @​dcastil in #​518
• Support for arbitrary CSS variable syntax by @​dcastil in #​518
• There are a bunch of new validators used by tailwind-merge, primarily for new Tailwind CSS v4 features like arbitrary CSS variables by @​dcastil in #​518

Bug Fixes

• Previously some order-sensitive modifiers like before: were treated as not order-sensitive. This is now fixed by @​dcastil in #​518

Documentation

• Added section explaining order-sensitive modifiers to configuration docs by @​dcastil in #​518

Full Changelog: dcastil/tailwind-merge@v2.6.0...v3.0.0

Thanks to @​brandonmcconnell, @​manavm1990, @​langy, @​jamesreaco, @​roboflow, @​syntaxfm, @​getsentry, @​codecov, @​sourcegraph and a private sponsor for sponsoring tailwind-merge! ❤️

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
aurora-web	Ready	Preview	Comment	Nov 9, 2025 2:44pm

[cloudflare-workers-and-pages]

Deploying aurora-web with    Cloudflare Pages

Latest commit:	b4c102c
Status:	🚫  Build failed.

View logs

[renovate]

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 3.x releases. But if you manually upgrade to 3.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.