Skip to content

Conversation

nerdy-tech-com-gitub
Copy link
Owner

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

snyk-top-banner

Snyk has created this PR to upgrade tailwindcss from 3.4.17 to 4.0.12.

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

  • The recommended version was released 25 days ago.

Release notes
Package name: tailwindcss
  • 4.0.12 - 2025-03-07

    Fixed

    • Vite: Fix url(…) rebasing in transitively imported CSS files (#16965)
    • PostCSS: Rebase url(…)s in imported CSS files (#16965)
    • Ensure utilities are sorted based on their actual property order (#16995)
    • Ensure strings in Pug and Slim templates are handled correctly (#17000)
    • Ensure classes between } and { are properly extracted (#17001)
    • Fix razor/cshtml pre-processing (#17027)
    • Ensure extracting candidates from JS embedded in a PHP string works as expected (#17031)
  • 4.0.11 - 2025-03-06

    Fixed

    • Ensure classes containing -- are extracted correctly (#16972)
    • Ensure classes containing numbers followed by dash or underscore are extracted correctly (#16980)
    • Ensure arbitrary container queries are extracted correctly (#16984)
    • Ensure classes ending in [ are extracted in Slim templating language (#16985)
    • Ensure arbitrary variables with data types are extracted correctly (#16986)
  • 4.0.10 - 2025-03-05

    Added

    • Add col-<number> and row-<number> utilities for grid-column and grid-row (#15183)

    Fixed

    • Ensure not-* does not remove :is(…) from variants (#16825)
    • Ensure @ keyframes are correctly emitted when using a prefix (#16850)
    • Don't swallow @ utility declarations when @ apply is used in nested rules (#16940)
    • Ensure outline-hidden behaves like outline-none outside of forced colors mode (#16943)
    • Allow !important on CSS variables again (#16873)
    • Vite: Do not crash when encountering an .svg file with # or ? in the filename (#16957)
    • Ensure utilities are properly detected within square brackets (#16306)
    • Ensure utilities are properly detected using Angular's conditional class binding syntax (#16306)
    • Ensure utilities starting with numbers are properly extracted from Slim templates (#16306)
    • Discard arbitrary property candidates that have guaranteed-invalid property names (#16306)

    Changed

    • Removed max-w-auto and max-h-auto utilities as they generate invalid CSS (#16917)
    • Replaced the existing candidate extractor with a brand new extractor to improve maintainability, correctness, and performance (#16306)
  • 4.0.9 - 2025-02-25

    Fixed

    • Make JS APIs available to plugins and configs in the Standalone CLI (#15934)
    • Vite: Don't crash when importing a virtual module from JavaScript that ends in .css (#16780)
    • Fix an issue where @ reference "…" would sometimes omit keyframe animations (#16774)
    • Ensure z-*! utilities are properly marked as !important (#16795)
    • Read UTF-8 CSS files that start with a byte-order mark (BOM) (#16800)
    • Ensure nested functions in selectors used with JavaScript plugins are not truncated (#16802)

    Changed

    • Emit variable fallbacks when using @ reference "…" instead of duplicate CSS variable declarations (#16774)
  • 4.0.8 - 2025-02-21

    Added

    • Allow @ import with theme(…) options for stylesheets that contain more than just @ theme rules (#16514)

    Fixed

    • Don't add !important to CSS variable declarations when using the important modifier (#16668)
    • Vite: Ignore files and directories specified in your .gitignore file when using automatic source detection(#16631)
    • Vite: Don't rely on the module graph for detecting candidates to ensure setups with multiple Vite builds work as expected (#16631)
    • Vite: Ensure Astro production builds always contain classes used in client-only components (#16631)
    • Vite: Always scan raw file contents for utility classes before any other transforms have been applied to ensure utility classes are scanned without any additional escaping (#16631)
    • Ensure utilities with more declarations are always sorted before utilities with fewer declarations when utilities only define CSS variables (#16715)
    • Only include translate-z-px utilities once in compiled CSS (#16718)

    Changed

    • Don't include theme variables that aren't used in compiled CSS (#16211, #16676)
  • 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
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.

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.4.17 to 4.0.12, a major version upgrade with potential breaking changes

New Features:

  • Added new grid utilities like col-<number> and row-<number> for grid-column and grid-row

Enhancements:

  • Replaced the existing candidate extractor with a new extractor to improve maintainability, correctness, and performance

Chores:

  • Updated Tailwind CSS dependency to the latest major version

Snyk has created this PR to upgrade tailwindcss from 3.4.17 to 4.0.12.

See this package in npm:
tailwindcss

See this project in Snyk:
https://app.snyk.io/org/nerds-github/project/ef708957-d107-4807-bb9b-ffb67ea15337?utm_source=github&utm_medium=referral&page=upgrade-pr
Copy link

sourcery-ai bot commented Apr 1, 2025

Reviewer's Guide by Sourcery

This pull request upgrades the tailwindcss dependency from version 3.4.3 to version 4.0.12. Review the changes to ensure compatibility and address any potential breaking changes introduced by the major version upgrade.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
The pull request upgrades the tailwindcss dependency from version 3.4.3 to version 4.0.12.
  • Updated the tailwindcss version in package.json.
dashboard/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