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 #973

Merged
merged 2 commits into from
Jul 31, 2024

Conversation

NiallJoeMaher
Copy link
Contributor

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 8 versions ahead of your current version.

  • The recommended version was released on 23 days 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.1d82a24b93b50392a3a3ed22281d5b18130b5fab - 2024-07-29
  • 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/nialljoemaher/project/8ac19f6c-c7f2-4720-acd1-09701979877c?utm_source=github&utm_medium=referral&page=upgrade-pr
@NiallJoeMaher NiallJoeMaher requested a review from a team as a code owner July 30, 2024 23:14
Copy link

vercel bot commented Jul 30, 2024

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

Name Status Preview Comments Updated (UTC)
codu ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jul 31, 2024 3:58am

Copy link
Contributor

coderabbitai bot commented Jul 30, 2024

Important

Review skipped

Ignore keyword(s) in the title.

Ignored keywords (1)
  • [Snyk]

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

Uh oh! @NiallJoeMaher, the image you shared is missing helpful alt text. Check your pull request body.

Alt text is an invisible description that helps screen readers describe images to blind or low-vision users. If you are using markdown to display images, add your alt text inside the brackets of the markdown image.

Learn more about alt text at Basic writing and formatting syntax: images on GitHub Docs.

@NiallJoeMaher NiallJoeMaher merged commit 75fe81d into develop Jul 31, 2024
3 of 4 checks passed
@NiallJoeMaher NiallJoeMaher deleted the snyk-upgrade-1a60334ac8ab012ac2ef53cbc041dc4d branch July 31, 2024 03:44
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