Tailwind Release Notes

Last updated: Dec 23, 2025

  • Dec 11, 2025
    • Parsed from source:
      Dec 11, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v4.1.18

    A robust set of fixes and compatibility upgrades improve validation, error reporting, and config handling across CSS parsing, Ruby checks, Vite integration, and CLI behavior. It expands theme and config support and strengthens canonicalization of utility classes.

    Fixed

    • Ensure validation of source(…) happens relative to the file it is in (#19274)
    • Include filename and line numbers in CSS parse errors (#19282)
    • Skip comments in Ruby files when checking for class names (#19243)
    • Skip over arbitrary property utilities with a top-level ! in the value (#19243)
    • Support environment API in @tailwindcss/vite (#18970)
    • Preserve case of theme keys from JS configs and plugins (#19337)
    • Write source maps correctly on the CLI when using --watch (#19373)
    • Handle special defaults (like ringColor.DEFAULT) in JS configs (#19348)
    • Improve backwards compatibility for content theme key from JS configs (#19381)
    • Upgrade: Handle future and experimental config keys (#19344)
    • Try to canonicalize any arbitrary utility to a bare value (#19379)
    • Validate candidates similarly to Oxide (#19397)
    • Canonicalization: combine text-* and leading-* classes (#19396)
    • Correctly handle duplicate CLI arguments (#19416)
    • Don’t emit color-mix fallback rules inside @keyframes (#19419)
    • CLI: Don't hang when output is /dev/stdout (#19421)
    Original source Report a problem
  • Dec 10, 2025
    • Parsed from source:
      Dec 10, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v3.4.19

    Fixed

    Don’t break sibling-*() functions when used inside calc(…) (#19335)

    Original source Report a problem
  • Nov 6, 2025
    • Parsed from source:
      Nov 6, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v4.1.17

    Fixed

    • Substitute @variant inside legacy JS APIs (#19263)
    • Prevent occasional crash on Windows when loaded into a worker thread (#19242)
    Original source Report a problem
  • Oct 23, 2025
    • Parsed from source:
      Oct 23, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v4.1.16

    Fixed

    • Discard candidates with an empty data type (#19172)
    • Fix canonicalization of arbitrary variants with attribute selectors (#19176)
    • Fix invalid colors due to nested & (#19184)
    • Improve canonicalization for & > :pseudo and & :pseudo arbitrary variants (#19178)
    Original source Report a problem
  • Oct 20, 2025
    • Parsed from source:
      Oct 20, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v4.1.15

    New release delivers robust bug fixes and upgrades across themes, utilities, and CSS tooling. Highlights include Safari devtools rendering fix, CSS warning suppression, improved theme key resolution, named groups support, and safer utilities with 0-value canonicalization and wrap-break-word migration. Postinstall script removed.

    Fixed

    • Fix Safari devtools rendering issue due to color-mix fallback (#19069)
    • Suppress Lightning CSS warnings about :deep, :slotted, and :global (#19094)
    • Fix resolving theme keys when starting with the name of another theme key in JS configs and plugins (#19097)
    • Allow named groups in combination with not-, has-, and in-* (#19100)
    • Prevent important utilities from affecting other utilities (#19110)
    • Don’t index into strings with the theme(…) function (#19111)
    • Fix parsing issue when \t is used in at-rules (#19130)
    • Upgrade: Canonicalize utilities containing 0 values (#19095)
    • Upgrade: Migrate deprecated break-words to wrap-break-word (#19157)

    Changed

    • Remove the postinstall script from oxide (#19149)
    Original source Report a problem
  • Oct 1, 2025
    • Parsed from source:
      Oct 1, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v4.1.14

    Tailwind CSS release fixes syntax issues and edge cases across ClojureScript, markdown directives, and templates while tightening file watchers and error handling. It streamlines grid and utility generation, adds better upgrade migrations, and improves warnings and theme handling for a smoother developer experience.

    Fixed

    • Handle ' syntax in ClojureScript when extracting classes (#18888)
    • Handle @variant inside @custom-variant (#18885)
    • Merge suggestions when using @utility (#18900)
    • Ensure that file system watchers created when using the CLI are always cleaned up (#18905)
    • Do not generate grid-column utilities when configuring grid-column-start or grid-column-end (#18907)
    • Do not generate grid-row utilities when configuring grid-row-start or grid-row-end (#18907)
    • Prevent duplicate CSS when overwriting a static utility with a theme key (#18056)
    • Show Lightning CSS warnings (if any) when optimizing/minifying (#18918)
    • Use default export condition for @tailwindcss/vite (#18948)
    • Re-throw errors from PostCSS nodes (#18373)
    • Detect classes in markdown inline directives (#18967)
    • Ensure files with only @theme produce no output when built (#18979)
    • Support Maud templates when extracting classes (#18988)
    • Upgrade: Do not migrate variant = 'outline' during upgrades (#18922)
    • Upgrade: Show version mismatch (if any) when running upgrade tool (#19028)
    • Upgrade: Ensure first class inside className is migrated (#19031)
    • Upgrade: Migrate classes inside *ClassName and *Class attributes (#19031)
    Original source Report a problem
  • Oct 1, 2025
    • Parsed from source:
      Oct 1, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v3.4.18

    Fixed

    • Improve support for raw supports-[…] queries in arbitrary values (#13605)
    • Fix require.cache error when loaded through a TypeScript file in Node 22.18+ (#18665)
    • Support import.meta.resolve(…) in configs for new enough Node.js versions (#18938)
    • Allow using newer versions of postcss-load-config for better ESM and TypeScript PostCSS config support with the CLI (#18938)
    • Remove irrelevant utility rules when matching important classes (#19030)
    Original source Report a problem
  • Sep 4, 2025
    • Parsed from source:
      Sep 4, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v4.1.13

    New release delivers stability fixes and upgrades across CSS handling, variant logic, and theming. Highlights include improved drop warnings, duplicate CSS removal, visibility transition tweaks, invalid variant rules, and upgrading to @custom-variant for aria, data, and supports themes.

    Changed
    Drop warning from browser build (#18731)
    Drop exact duplicate declarations when emitting CSS (#18809)
    Fixed
    Don't transition visibility when using transition (#18795)
    Discard matched variants with unknown named values (#18799)
    Discard matched variants with non-string values (#18799)
    Show suggestions for known matchVariant values (#18798)
    Replace deprecated clip with clip-path in sr-only (#18769)
    Hide internal fields from completions in matchUtilities (#18820)
    Ignore .vercel folders by default (can be overridden by @source … rules) (#18855)
    Consider variants starting with @- to be invalid (e.g. @-2xl:flex) (#18869)
    Do not allow custom variants to start or end with a - or _ (#18867, #18872)
    Upgrade: Migrate aria theme keys to @custom-variant (#18815)
    Upgrade: Migrate data theme keys to @custom-variant (#18816)
    Upgrade: Migrate supports theme keys to @custom-variant (#18817)

    Original source Report a problem
  • Aug 14, 2025
    • Parsed from source:
      Aug 14, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v4.1.12

    Tailwind CSS ships a wave of fixes and refinements across utilities, parsers, and tooling. Expect stronger reliability, clearer errors, and new opt‑outs, all boosting developer experience and compatibility.

    Fixed

    • Don't consider the global important state in @apply (#18404)
    • Add missing suggestions for flex- utilities (#18642)
    • Fix trailing ) from interfering with extraction in Clojure keywords (#18345)
    • Detect classes inside Elixir charlist, word list, and string sigils (#18432)
    • Track source locations through @plugin and @config (#18345)
    • Allow boolean values of process.env.DEBUG in @tailwindcss/node (#18485)
    • Ignore consecutive semicolons in the CSS parser (#18532)
    • Center the dropdown icon added to an input with a paired datalist by default (#18511)
    • Extract candidates in Slang templates (#18565)
    • Improve error messages when encountering invalid functional utility names (#18568)
    • Discard CSS AST objects with false or undefined properties (#18571)
    • Allow users to disable URL rebasing in @tailwindcss/postcss via transformAssetUrls: false (#18321)
    • Fix false-positive migrations in addEventListener and JavaScript variable names (#18718)
    • Fix Standalone CLI showing default Bun help when run via symlink on Windows (#18723)
    • Read from --border-color-* theme keys in divide-* utilities for backwards compatibility (#18704)
    • Don't scan .hdr and .exr files for classes by default (#18734)
    Original source Report a problem
  • Jun 26, 2025
    • Parsed from source:
      Jun 26, 2025
    • Detected by Releasebot:
      Dec 23, 2025
    Tailwind logo

    Tailwind

    v4.1.11

    Fixed

    • Add heuristic to skip candidate migrations inside emit(…) (#18330)
    • Extract candidates with variants in Clojure/ClojureScript keywords (#18338)
    • Document --watch=always in the CLI's usage (#18337)
    • Add support for Vite 7 to @tailwindcss/vite (#18384)
    Original source Report a problem

Related vendors