Skip to content
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

[Snyk] Upgrade tailwind-merge from 2.3.0 to 2.4.0 #180

Merged
merged 1 commit into from
Aug 25, 2024

Conversation

vigneshshettyin
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade tailwind-merge from 2.3.0 to 2.4.0.

ℹ️ 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.


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

  • The recommended version was released on a month ago.

Release notes
Package name: tailwind-merge
  • 2.4.0 - 2024-07-07

    New Features

    • Allow hooking into class parsing logic (experimental) by @ dcastil in #444
      • There is no info to this in the docs because this is experimental, but there is a new experimentalParseClassName property in the config that allows you to customize how tailwind-merge recognizes classes. If you're interested, you can read how to use it in the inline JSDocs and subscribe to #385 for upcoming more powerful low-level functionality.
    • Create security policy by @ dcastil in #439
      • Added documentation on how to report potential vulnerabilities
    • Avoid @ babel/runtime dependency by @ dcastil in #431
      • Now no dependencies in tailwind-merge anymore. This dependency was only used in the tailwind-merge/es5 bundle anyway which I don't optimize for.

    Documentation

    Other

    • Added GitHub Action that adds context-v2 label to every issue, discussion and PR by @ Pritam1211 in #434
    • Replace size-limit action with own metrics-report action by @ dcastil in #433

    Full Changelog: v2.3.0...v2.4.0

    Thanks to @ brandonmcconnell, @ manavm1990, @ langy, @ jamesreaco and @ microsoft for sponsoring tailwind-merge! ❤️

  • 2.4.0-dev.f745ace15e9a8cdf7815d9972858e5940c8db8b7 - 2024-07-07
  • 2.4.0-dev.f3b5d4a2acc36bef2a58f30c9808f3874fafc76d - 2024-07-29
  • 2.4.0-dev.4e3c37aebdee0d2619aed25af271f7f1482ce5c2 - 2024-07-07
  • 2.4.0-dev.488f9130f2ccc3696d37060104f967401b56da74 - 2024-07-29
  • 2.4.0-dev.38db48d362b45aab9ba7e2e05aef4c36abab6edb - 2024-07-24
  • 2.4.0-dev.31722ed18ba0f6f2edfe65a469664adb8ef2a77a - 2024-07-29
  • 2.4.0-dev.29b7592b391e73a0bd3bac75fc68b2ce12f65fef - 2024-08-11
  • 2.4.0-dev.1d82a24b93b50392a3a3ed22281d5b18130b5fab - 2024-07-29
  • 2.4.0-dev.0a332483114bb4ab4ec002262968ced86200ae23 - 2024-08-01
  • 2.3.0 - 2024-04-19

    New Features

    Documentation

    • Add tailwind-merge-go to similar packages in docs by @ Oudwins in #396

    Full Changelog: v2.2.2...v2.3.0

    Thanks to @ brandonmcconnell, @ manavm1990, @ langy and @ jamesreaco for sponsoring tailwind-merge! ❤️

from tailwind-merge GitHub release notes

Important

  • 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:

Snyk has created this PR to upgrade tailwind-merge from 2.3.0 to 2.4.0.

See this package in npm:
tailwind-merge

See this project in Snyk:
https://app.snyk.io/org/vigneshshettyin/project/f292640c-2272-4ab3-b7a3-dc7f2f3bba3e?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

vercel bot commented Aug 16, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
eat-my-url ✅ Ready (Inspect) Visit Preview 💬 Add feedback Aug 16, 2024 1:04pm

@vigneshshettyin vigneshshettyin merged commit 6bb072f into main Aug 25, 2024
7 checks passed
@VijeshVS VijeshVS deleted the snyk-upgrade-3d11b19b7ba00860259ba4ef0a9410f7 branch September 17, 2024 06:18
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