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 tailwindcss from 3.4.9 to 3.4.10 #25

Closed

Conversation

joaltoroc
Copy link
Contributor

snyk-top-banner

Snyk has created this PR to upgrade tailwindcss from 3.4.9 to 3.4.10.

ℹ️ 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 1 version ahead of your current version.

  • The recommended version was released on 22 days ago.

Release notes
Package name: tailwindcss
  • 3.4.10 - 2024-08-13

    Fixed

    • Bump versions of plugins in the Standalone CLI (#14185)
  • 3.4.9 - 2024-08-08

    Fixed

    • No longer warns when broad glob patterns are detecting vendor folders
from tailwindcss 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 tailwindcss from 3.4.9 to 3.4.10.

See this package in npm:
tailwindcss

See this project in Snyk:
https://app.snyk.io/org/joaltoroc/project/4c4ac2de-caf7-4472-b47d-7ed071e0bee5?utm_source=github&utm_medium=referral&page=upgrade-pr
@joaltoroc joaltoroc closed this Oct 1, 2024
@joaltoroc joaltoroc deleted the snyk-upgrade-b928c538c86d52264b1a8c02e058c538 branch October 1, 2024 03:48
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