Skip to content

[Snyk] Upgrade tailwindcss from 3.3.2 to 4.1.3 #785

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: master
Choose a base branch
from

Conversation

nerdy-tech-com-gitub
Copy link
Owner

@nerdy-tech-com-gitub nerdy-tech-com-gitub commented Apr 30, 2025

snyk-top-banner

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

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

  • The recommended version was released 25 days ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Denial of Service (DoS)
SNYK-JS-WS-7266574
169 Proof of Concept
high severity Excessive Platform Resource Consumption within a Loop
SNYK-JS-BRACES-6838727
169 Proof of Concept
high severity Inefficient Regular Expression Complexity
SNYK-JS-MICROMATCH-6838728
169 No Known Exploit
high severity Uncontrolled Recursion
SNYK-JS-NEXT-8186172
169 No Known Exploit
high severity Missing Authorization
SNYK-JS-NEXT-8520073
169 No Known Exploit
medium severity Missing Release of Resource after Effective Lifetime
SNYK-JS-INFLIGHT-6095116
169 Proof of Concept
medium severity Improper Input Validation
SNYK-JS-NANOID-8492085
169 No Known Exploit
medium severity Resource Exhaustion
SNYK-JS-NEXT-6032387
169 Proof of Concept
critical severity Improper Authorization
SNYK-JS-NEXT-9508709
169 Mature
medium severity Improper Input Validation
SNYK-JS-POSTCSS-5926692
169 No Known Exploit
medium severity Improper Input Validation
SNYK-JS-POSTCSS-5926692
169 No Known Exploit
Release notes
Package name: tailwindcss
  • 4.1.3 - 2025-04-04

    Fixed

    • Show warning when using unsupported bare value data type in --value(…) (#17464)
    • PostCSS: Ensure changes to the input CSS file don't generate stale output when using Turbopack (#17554)
    • Ensure classes are detected in Ruby's %w syntax in Slim templates (#17557)
  • 4.1.2 - 2025-04-03

    Fixed

    • Don't rely on the presence of @ layer base to polyfill @ property (#17506)
    • Support setting multiple inset shadows as arbitrary values (#17523)
    • Fix drop-shadow-* utilities that are defined with multiple shadows (#17515)
    • PostCSS: Fix race condition when two changes are queued concurrently (#17514)
    • PostCSS: Ensure files containing @ tailwind utilities are processed (#17514)
    • Ensure the color-mix(…) polyfill creates fallbacks even when using colors that cannot be statically analyzed (#17513)
    • Fix slow incremental builds with @ tailwindcss/vite and @ tailwindcss/postscss (especially on Windows) (#17511)
    • Vite: Fix missing CSS file in Qwik setups (#17533)
  • 4.1.1 - 2025-04-02

    Fixed

    • Disable padding in @ source inline(…) brace expansion (#17491)
    • Inject polyfills after @ import and body-less @ layer (#17493)
    • Ensure @ tailwindcss/cli does not contain an import for jiti (#17502)
  • 4.1.0 - 2025-04-01

    Added

    • Add details-content variant (#15319)
    • Add inverted-colors variant (#11693)
    • Add noscript variant (#11929, #17431)
    • Add items-baseline-last and self-baseline-last utilities (#13888, #17476)
    • Add pointer-none, pointer-coarse, and pointer-fine variants (#16946)
    • Add any-pointer-none, any-pointer-coarse, and any-pointer-fine variants (#16941)
    • Add safe alignment utilities (#14607)
    • Add user-valid and user-invalid variants (#12370)
    • Add wrap-anywhere, wrap-break-word, and wrap-normal utilities (#12128)
    • Add @ source inline(…) and @ source not inline(…) (#17147)
    • Add @ source not "…" (#17255)
    • Add text-shadow-* utilities (#17389)
    • Add mask-* utilities (#17134)
    • Add bg-{position,size}-* utilities for arbitrary values (#17432)
    • Add shadow-*/<alpha>, inset-shadow-*/<alpha>, drop-shadow-*/<alpha>, and text-shadow-*/<alpha> utilities to control shadow opacity (#17398, #17434)
    • Add drop-shadow-<color> utilities (#17434)
    • Improve compatibility with older versions of Safari and Firefox (#17435)

    Fixed

    • Follow symlinks when resolving @ source directives (#17391)
    • Don't scan ignored files for classes when changing an ignored file triggers a rebuild using @ tailwindcss/cli (#17255)
    • Support negated content rules in legacy JavaScript configuration (#17255)
    • Interpret syntax like @("@")md:… as @ md:… in Razor files (#17427)
    • Disallow top-level braces, top-level semicolons, and unbalanced parentheses and brackets in arbitrary values (#17361)
    • Ensure the --theme(…) function still resolves to the CSS variables when using legacy JS plugins (#17458)
    • Detect used theme variables in CSS module files (#17433, #17467)

    Changed

    • Ignore node_modules by default (can be overridden by @ source … rules) (#17255)
    • @ source rules that include file extensions or point inside node_modules/ folders no longer consider your .gitignore rules (#17255)
    • Deprecate bg-{left,right}-{top,bottom} in favor of bg-{top,bottom}-{left,right} utilities (#17378)
    • Deprecate object-{left,right}-{top,bottom} in favor of object-{top,bottom}-{left,right} utilities (#17437)
  • 4.0.17 - 2025-03-26

    Fixed

    • Fix an issue causing the CLI to hang when processing Ruby files (#17383)
  • 4.0.16 - 2025-03-25

    Added

    • Add support for literal values in --value('…') and --modifier('…') (#17304)

    Fixed

    • Fix class extraction followed by ( in Pug (#17320)
    • Ensure @ keyframes for theme animations are emitted if they are referenced following a comma (#17352)
    • Vite: Ensure that updates to an imported CSS file are properly propagated after updating source files (#17347)
    • Pre process Slim templates embedded in Ruby files (#17336)
    • Error when input and output files resolve to the same file when using the CLI (#17311)
    • Add missing suggestions when --spacing(--value(integer, number)) is used (#17308)
    • Add ::-webkit-details-marker pseudo to marker variant (#17362)
  • 4.0.15 - 2025-03-20

    Fixed

    • Fix incorrect angle in -bg-conic-* utilities (#17174)
    • Fix border-[12px_4px] being interpreted as a border-color instead of a border-width (#17248)
    • Work around a crash in Safari 16.4 and 16.5 when using the default Preflight styles (#17306)
    • Pre-process <template lang="…"> in Vue files (#17252)
    • Ensure that all CSS variables used by Preflight are prefixed (#17036)
    • Prevent segfault when loaded in a worker thread on Linux (#17276)
    • Ensure multiple --value(…) or --modifier(…) calls don't delete subsequent declarations (#17273)
    • Fix class extraction followed by ( in Slim (#17278)
    • Export PluginUtils from tailwindcss/plugin for compatibility with v3 (#17299)
    • Remove redundant line-height: initial from Preflight (#15212)
    • Increase Standalone hardware compatibility on macOS x64 builds (#17267)
    • Ensure that the CSS file rebuilds if a new CSS variable is used from templates (#17301)

    Changed

    • The --theme(…) function now returns CSS variables from your theme variables unless used inside positions where CSS variables are invalid (e.g. inside @ media queries) (#17036)
  • 4.0.14 - 2025-03-13

    Fixed

    • Do not extract candidates with JS string interpolation ${ (#17142)
    • Fix extraction of variants containing . character (#17153)
    • Fix extracting candidates in Clojure/ClojureScript (#17087)
  • 4.0.13 - 2025-03-11

    Fixed

    • Fix Haml pre-processing (#17051)
    • Ensure .node and .wasm files are not scanned for utilities (#17123)
    • Improve performance when scanning JSON files (#17125)
    • Fix extracting candidates containing dots in Haml, Pug, and Slim pre processors (#17094, #17085, #17113)
    • Don't create invalid CSS when encountering a link wrapped in square brackets (#17129)
  • 4.0.12 - 2025-03-07
  • 4.0.11 - 2025-03-06
  • 4.0.10 - 2025-03-05
  • 4.0.9 - 2025-02-25
  • 4.0.8 - 2025-02-21
  • 4.0.7 - 2025-02-18
  • 4.0.6 - 2025-02-10
  • 4.0.5 - 2025-02-08
  • 4.0.4 - 2025-02-06
  • 4.0.3 - 2025-02-01
  • 4.0.2 - 2025-01-31
  • 4.0.1 - 2025-01-29
  • 4.0.0 - 2025-01-21
  • 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
  • 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

  • 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

Upgrade Tailwind CSS from version 3.3.2 to 4.1.3, addressing multiple security vulnerabilities

New Features:

  • Added support for new Tailwind CSS 4.x features

Bug Fixes:

  • Resolved multiple high and medium severity security vulnerabilities

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

See this package in npm:
tailwindcss

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/d4657084-9e05-4c20-b3a3-bb8f25b2b8bc?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sourcery-ai bot commented Apr 30, 2025

Reviewer's Guide

This pull request upgrades the tailwindcss dependency from version 3.3.2 to 4.1.3 by updating the version specified in the package.json file. This automated update by Snyk addresses several security vulnerabilities and incorporates numerous features and fixes introduced across 91 intermediate versions.

File-Level Changes

Change Details Files
Upgrade tailwindcss dependency version.
  • Updated tailwindcss version from 3.3.2 to 4.1.3.
examples/slack-clone/nextjs-slack-clone/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!

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

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