chore(deps): bump tailwind-merge from 2.6.1 to 3.6.0 - #158
chore(deps): bump tailwind-merge from 2.6.1 to 3.6.0#158dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [tailwind-merge](https://github.com/dcastil/tailwind-merge) from 2.6.1 to 3.6.0. - [Release notes](https://github.com/dcastil/tailwind-merge/releases) - [Commits](dcastil/tailwind-merge@v2.6.1...v3.6.0) --- updated-dependencies: - dependency-name: tailwind-merge dependency-version: 3.6.0 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
There was a problem hiding this comment.
1 issue found across 1 file
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="package.json">
<violation number="1" location="package.json:105">
P1: tailwind-merge v3 drops support for Tailwind CSS v3 entirely. Since this project uses Tailwind CSS v3.4.17, upgrading from v2 to v3 will cause incorrect class merging for v3-specific classes and class patterns. The official docs explicitly advise against this upgrade if staying on Tailwind CSS v3.</violation>
</file>
Reply with feedback, questions, or to request a fix.
Re-trigger cubic
| "sip.js": "0.21.2", | ||
| "sonner": "^1.7.4", | ||
| "tailwind-merge": "^2.6.0", | ||
| "tailwind-merge": "^3.6.0", |
There was a problem hiding this comment.
P1: tailwind-merge v3 drops support for Tailwind CSS v3 entirely. Since this project uses Tailwind CSS v3.4.17, upgrading from v2 to v3 will cause incorrect class merging for v3-specific classes and class patterns. The official docs explicitly advise against this upgrade if staying on Tailwind CSS v3.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At package.json, line 105:
<comment>tailwind-merge v3 drops support for Tailwind CSS v3 entirely. Since this project uses Tailwind CSS v3.4.17, upgrading from v2 to v3 will cause incorrect class merging for v3-specific classes and class patterns. The official docs explicitly advise against this upgrade if staying on Tailwind CSS v3.</comment>
<file context>
@@ -102,7 +102,7 @@
"sip.js": "0.21.2",
"sonner": "^1.7.4",
- "tailwind-merge": "^2.6.0",
+ "tailwind-merge": "^3.6.0",
"tailwindcss-animate": "^1.0.7",
"uuid": "^14.0.0",
</file context>
| "tailwind-merge": "^3.6.0", | |
| "tailwind-merge": "^2.6.0", |
Bumps tailwind-merge from 2.6.1 to 3.6.0.
Release notes
Sourced from tailwind-merge's releases.
... (truncated)
Commits
d54f7e5v3.6.0638871aUpdate README to add info about Tailwind CSS v4.3 support39fc7b5Revert "v3.6.0"bd8390fv3.6.0802877cadd v3.6.0 changeloga35fedaMerge pull request #665 from dcastil/renovate/rollup-plugin-babel-7.x940389cMerge pull request #667 from dcastil/renovate/release-drafter-release-drafter...005af6dpin to specific version5816cedimplement breaking changes17041e1Merge pull request #676 from dcastil/dependabot/npm_and_yarn/babel/plugin-tra...Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)Summary by cubic
Upgrade
tailwind-mergefrom 2.6.1 to 3.6.0 to align with Tailwind CSS v4.2/v4.3 and improve class merging (incl. support for utilities like named container queries).Dependencies
tailwind-merge2.6.1 → 3.6.0Migration
twMergeusage.createTailwindMergeconfig, review v3 docs and considerpostfixLookupClassGroupsfor slash-in-class utilities.Written for commit cdbb293. Summary will update on new commits. Review in cubic