Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.6.0->^3.0.0Release Notes
dcastil/tailwind-merge (tailwind-merge)
v3.0.1Compare Source
Bug Fixes
b9c136de22885eFull Changelog: dcastil/tailwind-merge@v3.0.0...v3.0.1
Thanks to @brandonmcconnell, @manavm1990, @langy, @jamesreaco, @roboflow, @syntaxfm, @getsentry, @codecov and a private sponsor for sponsoring tailwind-merge! ❤️
v3.0.0Compare 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
isLengthvalidator was removed and split into separate validatorsisNumberandisFractionby @dcastil in https://github.com/dcastil/tailwind-merge/pull/518-character anymore by @dcastil in https://github.com/dcastil/tailwind-merge/pull/518orderSensitiveModifiersproperty in config when usingcreateTailwindMergeby @dcastil in https://github.com/dcastil/tailwind-merge/pull/518DefaultThemeGroupIdstype union consists of different string literals than before by @dcastil in https://github.com/dcastil/tailwind-merge/pull/518New Features
Bug Fixes
before:were treated as not order-sensitive. This is now fixed by @dcastil in https://github.com/dcastil/tailwind-merge/pull/518Documentation
Full Changelog: dcastil/tailwind-merge@v2.6.0...v3.0.0
Thanks to @brandonmcconnell, @manavm1990, @langy, @jamesreaco, @roboflow, @syntaxfm, @getsentry, @codecov and a private sponsor for sponsoring tailwind-merge! ❤️
Configuration
📅 Schedule: Branch creation - "every weekend" (UTC), 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.
This PR was generated by Mend Renovate. View the repository job log.