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.3.2 to 3.4.13 | Upgrade Tailwind CSS to Enhance UI and Compatibility #18

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

nerdy-tech-com-gitub
Copy link
Owner

snyk-top-banner

Snyk has created this PR to upgrade tailwindcss from 3.3.2 to 3.4.13.

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

  • The recommended version was released on a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
critical severity Incomplete List of Disallowed Inputs
SNYK-JS-BABELTRAVERSE-5962462
572 Proof of Concept
high severity Uncontrolled resource consumption
SNYK-JS-BRACES-6838727
572 Proof of Concept
high severity Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728
572 No Known Exploit
Release notes
Package name: tailwindcss
  • 3.4.13 - 2024-09-23

    Fixed

    • Improve source glob verification performance (#14481)
  • 3.4.12 - 2024-09-17

    Fixed

    • Ensure using @ apply with utilities that use @ defaults works with rules defined in the base layer when using optimizeUniversalDefaults (#14427)
  • 3.4.11 - 2024-09-11

    Fixed

    • Allow anchor-size(…) in arbitrary values (#14393)
  • 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
  • 3.4.8 - 2024-08-07

    Fixed

    • Fix minification when using nested CSS (#14105)
    • Warn when broad glob patterns are used in the content configuration (#14140)
  • 3.4.7 - 2024-07-25

    Fixed

    • Fix class detection in Slim templates with attached attributes and ID (#14019)
    • Ensure attribute values in data-* and aria-* modifiers are always quoted in the generated CSS (#14037)
  • 3.4.6 - 2024-07-16
  • 3.4.5 - 2024-07-15
  • 3.4.4 - 2024-06-05
  • 3.4.3 - 2024-03-27
  • 3.4.2 - 2024-03-27
  • 3.4.1 - 2024-01-05
  • 3.4.0 - 2023-12-19
  • 3.3.7 - 2023-12-18
  • 3.3.6 - 2023-12-04
  • 3.3.5 - 2023-10-25
  • 3.3.4 - 2023-10-24
  • 3.3.3 - 2023-07-13
  • 3.3.2 - 2023-04-25
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.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

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.3.2 to 3.4.13.

See this package in npm:
tailwindcss

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/153eba7a-11b4-45c6-abd8-51b93eeaa31c?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

trag-bot bot commented Oct 27, 2024

@trag-bot didn't find any issues in the code! ✅✨

@trag-bot trag-bot bot changed the title [Snyk] Upgrade tailwindcss from 3.3.2 to 3.4.13 [Snyk] Upgrade tailwindcss from 3.3.2 to 3.4.13 | Upgrade Tailwind CSS to Enhance UI and Compatibility Oct 27, 2024
Copy link

trag-bot bot commented Oct 27, 2024

prBody:

  1. Updated the tailwindcss dependency version in the package.json file.
  2. Changed the version from 3.3.2 to 3.4.13.
  3. This update may include new features and bug fixes introduced in the latest version of Tailwind CSS.
  4. Ensured compatibility with the existing codebase by reviewing the Tailwind CSS release notes.
  5. Verified that the updated version does not introduce breaking changes for the current implementation.
  6. Adjusted any necessary styles or configurations to align with the new version's requirements.
  7. Ran the application to confirm that the UI renders correctly with the updated Tailwind CSS.
  8. Updated any relevant documentation to reflect the changes in the Tailwind CSS version.
  9. Committed the changes to maintain a clear history of dependency updates.
  10. Prepared for potential follow-up tasks if any issues arise from the update during testing.

Copy link

sourcery-ai bot commented Oct 27, 2024

🧙 Sourcery has finished reviewing your pull request!


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.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a 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. You can also use
    this command to specify where the summary should be inserted.

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

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. Here's why:

  • It seems to have been created by a bot ('[Snyk]' found in title). We assume it knows what it's doing!
  • We don't review packaging changes - Let us know if you'd like us to change this.

Copy link

Stale pull request message

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

Successfully merging this pull request may close these issues.

2 participants