Update tailwind-merge 3.4.0 β 3.5.0 (minor)#409
Conversation
|
The files' contents are under analysis for test generation. |
|
Infisical secrets check: β No secrets leaked! π» Scan logs2026-02-20T00:55:43Z INF scanning for exposed secrets...
12:55AM INF 369 commits scanned.
2026-02-20T00:55:43Z INF scan completed in 363ms
2026-02-20T00:55:43Z INF no leaks found
|
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Caution Review the following alerts detected in dependencies. According to your organization's Security Policy, you must resolve all "Block" alerts before proceeding. Learn more about Socket for GitHub.
|
DeepSource reviewed changes in the commit range For detailed review results, please see the PR on DeepSourceΒ β PR Report Card
Code Review Summary
How are these analyzer statuses calculated?Administrators can configure which issue categories are reported and cause analysis to be marked as failed when detected. This helps prevent bad and insecure code from being introduced in the codebase. If you're an administrator, you can modify this in the repository's settings. |
guibranco
left a comment
There was a problem hiding this comment.
Automatically approved by gstraccini[bot]
|
@depfu merge |



Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.
What changed?
β³οΈ tailwind-merge (3.4.0 β 3.5.0) Β· Repo
Release Notes
3.5.0
3.4.1
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by more commits than we can show here.
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase.All Depfu comment commands