Skip to content

[Snyk] Upgrade tailwind-merge from 2.6.0 to 3.3.1 #160

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.

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
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nerdy-tech-com-gitub
Copy link
Owner

@nerdy-tech-com-gitub nerdy-tech-com-gitub commented Jul 3, 2025

snyk-top-banner

Snyk has created this PR to upgrade tailwind-merge from 2.6.0 to 3.3.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.


⚠️ Warning: This PR contains major version upgrade(s), and may be a breaking change.

  • The recommended version is 50 versions ahead of your current version.

  • The recommended version was released 22 days ago.

Release notes
Package name: tailwind-merge
  • 3.3.1 - 2025-06-10

    Bug Fixes

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

    Full Changelog: 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! ❤️

  • 3.3.1-dev.40d8feed6aafd389eed0a20acb6d9e174fe2fa24 - 2025-06-10
  • 3.3.1-dev.229ad664b2d06610f2cdb8c9d66215a78b3ac9e1 - 2025-06-17
  • 3.3.0 - 2025-05-11

    New Features

    Full Changelog: 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! ❤️

  • 3.3.0-dev.d3df8775ccd86c48fa7abafbe069220f1c3e854e - 2025-06-10
  • 3.3.0-dev.ceb3b4aea113281e75b39f20e40fd1d16e0727be - 2025-05-11
  • 3.3.0-dev.c3d7208367b8f1b9c0878b540433a2a6c438ad98 - 2025-05-15
  • 3.3.0-dev.47155f0ebe17188991c8cafc9fe2ae034b18265c - 2025-06-01
  • 3.2.0 - 2025-04-06

    New Features

    Full Changelog: 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! ❤️

  • 3.2.0-dev.ff769f3e6d5016596fc294f8fd785d857c4a588b - 2025-04-06
  • 3.2.0-dev.b4d2ed6cce4616a16f13a08e4451fc573482e2b1 - 2025-05-01
  • 3.2.0-dev.ac1d9187181d9e75c3e6ebdb409d52fe0e383930 - 2025-05-11
  • 3.2.0-dev.992816e1c8c98ba0ed38e02bd55fb960e02ac5e4 - 2025-04-11
  • 3.2.0-dev.8c2f180908f8ceda7ff766c596f7f0bb9e4ba944 - 2025-05-11
  • 3.2.0-dev.421f4f219fd0373ae0f665bef2a624da7e94309d - 2025-04-30
  • 3.1.0 - 2025-03-31

    New Features

    Bug Fixes

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

    Documentation

    Other

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

    Full Changelog: 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! ❤️

  • 3.1.0-dev.dd2e767d1f6520b2d368423f93341215cd6ba869 - 2025-03-31
  • 3.1.0-dev.bea75e72a7b662033f8437a00a0f4d16e178bcf7 - 2025-04-01
  • 3.1.0-dev.b7527c4868c034a76ff65286f1cb03a9e01e990b - 2025-04-04
  • 3.1.0-dev.a3f14e5b69c3d57742c879da90ba15c34326681b - 2025-03-31
  • 3.1.0-dev.858ad0eecd9efa3f9d5de6ce807a51436e2fc6cc - 2025-04-06
  • 3.0.2 - 2025-02-22

    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: 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! ❤️

  • 3.0.2-dev.fd635e144baa4c60bff138a35c096ea7403053a0 - 2025-03-09
  • 3.0.2-dev.f4eacb6bc1800031147a153fcf20e586b277320e - 2025-03-01
  • 3.0.2-dev.d833c72511a0a44cf0aa8eacd2915d4d7fc1f602 - 2025-03-09
  • 3.0.2-dev.d6ef6761514d6f24d1d4c66d8dd823350c2dd019 - 2025-03-01
  • 3.0.2-dev.cb8392fb6e788ee12275b40d9b0f8e0f3adbe66e - 2025-03-22
  • 3.0.2-dev.b7721dc13a6c9cb477eaddd48330d95bd3506023 - 2025-03-31
  • 3.0.2-dev.b5423b8174eea318d36577080388945b4b74999a - 2025-02-22
  • 3.0.2-dev.51b3c3a71336978b17500091c20fe8f50eda1cc3 - 2025-03-21
  • 3.0.2-dev.336458f49522f0d7574ffbdd33b9fef6a90b563e - 2025-03-23
  • 3.0.2-dev.2e63b238d620e867eb7e4db19680d90877085786 - 2025-03-25
  • 3.0.2-dev.0f3ecff584b8c57c5ecc41b72966e28e5ea19ef2 - 2025-03-31
  • 3.0.1 - 2025-01-30

    Bug Fixes

    Full Changelog: 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! ❤️

  • 3.0.1-dev.f3cdb9523f5f5a9bcf40e12e95846afda5f534a5 - 2025-02-02
  • 3.0.1-dev.e80f256fb5654a2812ad9c326ec67370b4c7c18c - 2025-02-02
  • 3.0.1-dev.e5eec552db5af11764f352daa7750fe8cc73aae7 - 2025-01-30
  • 3.0.1-dev.d862881bc0cb556d80956f50d253cdd4fe56d33c - 2025-02-20
  • 3.0.1-dev.981832488bd2a25ed0a8cab9d4b451bc6d0ef324 - 2025-02-10
  • 3.0.1-dev.7e8e9fe0466fb4d264ca09ea4fbeea55524f4481 - 2025-02-12
  • 3.0.1-dev.7761e42bd62d8382eebf61d3e4c69e1fec5cc2ab - 2025-02-12
  • 3.0.1-dev.6a90675ee3532f1e8b3c6e00ae120c295177bbf2 - 2025-02-05
  • 3.0.1-dev.493fa8c11046249332aa42e9269affdb786023a1 - 2025-01-30
  • 3.0.1-dev.431c42ad661a55c5908c8a76e5b9f525bf301b18 - 2025-02-15
  • 3.0.1-dev.417192012b63f28d01c76c858a50e67a594b7ef6 - 2025-02-15
  • 3.0.1-dev.2e8f3d5a7476f89e779498565eadc212fec25877 - 2025-02-20
  • 3.0.1-dev.2475d15b5a69e9fe68efc16ac19b4928a63de8ae - 2025-02-22
  • 3.0.0 - 2025-01-30

    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

    Full Changelog: 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! ❤️

  • 3.0.0-dev.e22885e41e1661f1493f9bf6fb829cfbe1b50281 - 2025-01-30
  • 3.0.0-dev.7378c16adcc261599fa2debe8c18d77071c946f4 - 2025-01-30
  • 2.6.0 - 2024-12-23

    New Features

    Full Changelog: v2.5.5...v2.6.0

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

from tailwind-merge GitHub release notes

Important

  • Warning: This PR contains a major version upgrade, and may be a breaking change.
  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Summary by Sourcery

Build:

  • Bump tailwind-merge from ^2.2.1 to ^3.3.1

Snyk has created this PR to upgrade tailwind-merge from 2.6.0 to 3.3.1.

See this package in npm:
tailwind-merge

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/a394135e-c792-439f-9f41-49d0d885a64e?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sourcery-ai bot commented Jul 3, 2025

Reviewer's Guide

This PR performs a major version upgrade of the tailwind-merge dependency in the documentation site’s package.json, updating the version spec from v2.x to v3.3.1. The change is limited to the dependency declaration, with any lockfile updates applied alongside. No other source files or code logic have been modified.

File-Level Changes

Change Details Files
Bump tailwind-merge dependency to v3.3.1
  • Update version spec from "^2.2.1" to "^3.3.1"
docs/docs.trychroma.com/package.json

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants