Skip to content

[Snyk] Upgrade tailwindcss from 3.4.4 to 4.0.6 #46

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 Mar 5, 2025

snyk-top-banner

Snyk has created this PR to upgrade tailwindcss from 3.4.4 to 4.0.6.

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

  • The recommended version was released 23 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
131 Proof of Concept
medium severity Improper Input Validation
SNYK-JS-NANOID-8492085
131 No Known Exploit
Release notes
Package name: tailwindcss
  • 4.0.6 - 2025-02-10

    Fixed

    • Revert change to no longer include theme variables that aren't used in compiled CSS (#16403)
  • 4.0.5 - 2025-02-08

    Added

    • Add @ theme static option for always including theme variables in compiled CSS (#16211)

    Fixed

    • Remove rogue console.log from @ tailwindcss/vite (#16307)

    Changed

    • Don't include theme variables that aren't used in compiled CSS (#16211)
  • 4.0.4 - 2025-02-06

    Fixed

    • Fix a crash when setting JS theme values to null (#16210)
    • Ensure escaped underscores in CSS variables in arbitrary values are properly unescaped (#16206)
    • Ensure that the containers JS theme key is added to the --container-* namespace (#16169)
    • Ensure theme @ keyframes are generated even if an --animation-* variable spans multiple lines (#16237)
    • Vite: Skip parsing stylesheets with the ?commonjs-proxy flag (#16238)
    • Fix order-first and order-last for Firefox (#16266)
    • Fix support for older instruction sets on Linux x64 builds of the standalone CLI (#16244)
    • Ensure NODE_PATH is respected when resolving JavaScript and CSS files (#16274)
    • Ensure Node addons are packaged correctly with FreeBSD builds (#16277)
    • Fix an issue where @ variant inside a referenced stylesheet could cause a stack overflow (#16300)
  • 4.0.3 - 2025-02-01

    Fixed

    • Fix incorrect removal of @ import url(); (#16144)
  • 4.0.2 - 2025-01-31

    Fixed

    • Only generate positive grid-cols-* and grid-rows-* utilities (#16020)
    • Ensure escaped theme variables are handled correctly (#16064)
    • Ensure we process Tailwind CSS features when only using @ reference or @ variant (#16057)
    • Refactor gradient implementation to work around prettier/prettier#17058 (#16072)
    • Vite: Ensure hot-reloading works with SolidStart setups (#16052)
    • Vite: Fix a crash when starting the development server in SolidStart setups (#16052)
    • Vite: Don't rebase URLs that appear to be aliases (#16078)
    • Vite: Transform <style> blocks in HTML files (#16069)
    • Prevent camel-casing CSS custom properties added by JavaScript plugins (#16103)
    • Do not emit @ keyframes in @ theme reference (#16120)
    • Discard invalid declarations when parsing CSS (#16093)
    • Do not emit empty CSS rules and at-rules (#16121)
    • Handle @ variant when at the top-level of a stylesheet (#16129)
  • 4.0.1 - 2025-01-29

    Added

    • Include :open pseudo-class in existing open variant (#15349)

    Fixed

    • Remove invalid min-w/h-none utilities (#15845)
    • Discard CSS variable shorthand utilities that don't use valid CSS variables (#15738)
    • Ensure font-size utilities with none modifier have a line-height set e.g. text-sm/none (#15921)
    • Ensure font-size utilities with unknown modifier don't generate CSS (#15921)
    • Don’t suggest font weight utilities more than once (#15857)
    • Suggest container query variants (#15857)
    • Disable bare value suggestions when not using the --spacing variable (#15857)
    • Ensure suggested classes are properly sorted (#15857)
    • Don’t look at .gitignore files outside initialized repos (#15941)
    • Find utilities when using the Svelte class shorthand syntax across multiple lines (#15974)
    • Find utilities when using the Angular class shorthand syntax (#15974)
    • Find utilities when using functions inside arrays (#15974)
    • Ensure that @ tailwindcss/browser does not pollute the global namespace (#15978)
    • Ensure that tailwind-merge is not scanned when using the Vite plugin (#16005)
    • Ensure CSS theme variables are available within shadow roots (#15975)
    • Fix crash when project lives in the / directory (#15988)
    • Ensure custom variants have a non-empty selector list (#16009)
    • Upgrade: Ensure JavaScript config files on different drives are correctly migrated (#15927)
    • Upgrade: Migrate leading-[1] to leading-none (#16004)
    • Upgrade: Do not migrate arbitrary leading utilities to bare values (#16004)
  • 4.0.0 - 2025-01-21

    Holy shit it's actually done — we just tagged Tailwind CSS v4.0.

    Tailwind CSS v4.0 is an all-new version of the framework optimized for performance and flexibility, with a reimagined configuration and customization experience, and taking full advantage of the latest advancements the web platform has to offer.

    Start using Tailwind CSS v4.0 today by installing it in a new project, or playing with it directly in the browser on Tailwind Play.

    For existing projects, we've published a comprehensive upgrade guide and built an automated upgrade tool to get you on the latest version as quickly and painlessly as possible.

    For a deep-dive into everything that's new, check out the announcement post.

  • 4.0.0-beta.10 - 2025-01-21
  • 4.0.0-beta.9 - 2025-01-09
  • 4.0.0-beta.8 - 2024-12-17
  • 4.0.0-beta.7 - 2024-12-13
  • 4.0.0-beta.6 - 2024-12-06
  • 4.0.0-beta.5 - 2024-12-04
  • 4.0.0-beta.4 - 2024-11-29
  • 4.0.0-beta.3 - 2024-11-27
  • 4.0.0-beta.2 - 2024-11-22
  • 4.0.0-beta.1 - 2024-11-21
  • 4.0.0-alpha.36 - 2024-11-21
  • 4.0.0-alpha.35 - 2024-11-20
  • 4.0.0-alpha.34 - 2024-11-14
  • 4.0.0-alpha.33 - 2024-11-12
  • 4.0.0-alpha.32 - 2024-11-11
  • 4.0.0-alpha.31 - 2024-10-30
  • 4.0.0-alpha.30 - 2024-10-24
  • 4.0.0-alpha.29 - 2024-10-23
  • 4.0.0-alpha.28 - 2024-10-17
  • 4.0.0-alpha.27 - 2024-10-15
  • 4.0.0-alpha.26 - 2024-10-03
  • 4.0.0-alpha.25 - 2024-09-24
  • 4.0.0-alpha.24 - 2024-09-12
  • 4.0.0-alpha.23 - 2024-09-05
  • 4.0.0-alpha.22 - 2024-09-05
  • 4.0.0-alpha.21 - 2024-09-02
  • 4.0.0-alpha.20 - 2024-08-23
  • 4.0.0-alpha.19 - 2024-08-09
  • 4.0.0-alpha.18 - 2024-07-25
  • 4.0.0-alpha.17 - 2024-07-04
  • 4.0.0-alpha.16 - 2024-06-07
  • 4.0.0-alpha.15 - 2024-05-08
  • 4.0.0-alpha.14 - 2024-04-09
  • 4.0.0-alpha.13 - 2024-04-04
  • 4.0.0-alpha.12 - 2024-04-04
  • 4.0.0-alpha.11 - 2024-03-27
  • 4.0.0-alpha.10 - 2024-03-21
  • 4.0.0-alpha.9 - 2024-03-13
  • 4.0.0-alpha.8 - 2024-03-11
  • 4.0.0-alpha.7 - 2024-03-08
  • 4.0.0-alpha.6 - 2024-03-07
  • 4.0.0-alpha.5 - 2024-03-06
  • 4.0.0-alpha.4 - 2024-03-06
  • 4.0.0-alpha.3 - 2024-03-06
  • 4.0.0-alpha.2 - 2024-03-06
  • 4.0.0-alpha.1 - 2024-03-05
  • 3.4.17 - 2024-12-17
  • 3.4.16 - 2024-12-03
  • 3.4.15 - 2024-11-14
  • 3.4.14 - 2024-10-15
  • 3.4.13 - 2024-09-23
  • 3.4.12 - 2024-09-17
  • 3.4.11 - 2024-09-11
  • 3.4.10 - 2024-08-13
  • 3.4.9 - 2024-08-08
  • 3.4.8 - 2024-08-07
  • 3.4.7 - 2024-07-25
  • 3.4.6 - 2024-07-16
  • 3.4.5 - 2024-07-15
  • 3.4.4 - 2024-06-05
from tailwindcss 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.
  • 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:

Summary by Sourcery

Bug Fixes:

  • Fixes for multiple vulnerabilities including 'Missing Release of Resource after Effective Lifetime' and 'Improper Input Validation'.

Snyk has created this PR to upgrade tailwindcss from 3.4.4 to 4.0.6.

See this package in npm:
tailwindcss

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/ded0d4c9-2f65-458e-91a2-4bc521804eb9?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sourcery-ai bot commented Mar 5, 2025

Reviewer's Guide by Sourcery

This pull request upgrades the tailwindcss dependency from version 3.4.4 to 4.0.6. The update was performed by Snyk and includes potential breaking changes due to the major version upgrade. Review the release notes for tailwindcss version 4.0.6 to understand the changes and ensure compatibility with the project.

Updated class diagram for Tailwind CSS configuration

classDiagram
    class TailwindConfig {
        .. v3.4.4 ..
        + content: string[]
        + theme: object
        + plugins: any[]

        .. v4.0.6 ..
        + config: string // Path to CSS config file
        + theme: CSSVariables
        + extend: CSSVariables
    }

    class CSSVariables {
      + --color-primary: #007bff
      + --font-size-base: 1rem
      + ...
    }

    note for TailwindConfig "Tailwind CSS v4.0 uses a CSS-first configuration approach, replacing the JavaScript configuration file with a CSS file."
Loading

File-Level Changes

Change Details Files
The pull request upgrades the tailwindcss dependency from version 3.4.4 to 4.0.6.
  • Updated the tailwindcss version in package.json.
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!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

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.

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