What changed in tailwindcss, release by release
The lines under each release are tailwindcss's own release-note bullets with pull request numbers, names and links removed, grouped by its own headings. Wording is theirs. Not affiliated with tailwindcss.
v4.3.5
- FixedCanonicalization: improve performance in projects with many functional variant values (e.g. a matchVariant plugin with thousands of values)
- FixedDon't crash or create a fallback with the wrong color for a color-mix without a color interpolation method (e.g. color-mix(var(--color-red-500)) or…
v4.3.4
- NewAdd /turbopack, a Turbopack loader for using Tailwind CSS with Next.js
- FixedEnsure watch mode detects changes to symlinked files whose real paths aren't otherwise scanned
- FixedEnsure variants using wrap generated utilities instead of nesting inside them
v4.3.3
- FixedSupport --watch --poll[=ms] in /cli when filesystem events are unreliable or unavailable
- FixedCanonicalization: match arbitrary hex colors against theme colors case-insensitively (e.g. bg-[#fff] and bg-[#FFF] → bg-white)
v4.3.2
- FixedSupport bare spacing values for auto-rows-* and auto-cols-* utilities (e.g. auto-rows-12 and auto-cols-16)
- FixedPrevent /cli in --watch mode from crashing on Windows when points to a directory that doesn't exist
v4.3.1
- NewAdd --silent option to suppress output in /cli
- FixedRemove deprecation warnings by using Module#registerHooks instead of Module#register on Node 26+
- FixedCanonicalization: don't crash when plugin utilities throw for unsupported values
- ChangedGenerate 0 instead of calc(var(--spacing) * 0) for spacing utilities like m-0 and left-0
- ChangedGenerate var(--spacing) instead of calc(var(--spacing) * 1) for spacing utilities like m-1 and left-1
v4.3.0
- NewAdd scrollbar-{auto,thin,none} utilities for scrollbar-width, and scrollbar-thumb-* / scrollbar-track-* color utilities for scrollbar-color
- NewAdd scrollbar-gutter-* utilities
- FixedEnsure resolves package JavaScript entries instead of browser CSS entries when using /vite
- FixedFix relative and paths resolving from the wrong directory when using /vite
v4.2.4
- FixedEnsure imports in and still resolve correctly when using Vite aliases in /vite
v4.2.3
- FixedCanonicalization: improve canonicalizations for tracking-* utilities by preferring non-negative utilities (e.g. -tracking-tighter → tracking-wider)
- FixedFix crash due to invalid characters in candidate (exceeding valid unicode code point range)
v4.2.2
- NewSupport Vite 8 in /vite
- FixedDon't crash when candidates contain prototype properties like row-constructor
- FixedCanonicalize calc(var(--spacing)*…) expressions into --spacing
v4.2.1
- FixedAllow trailing dash in functional utility names for backwards compatibility
- FixedProperly detect classes containing . characters within curly braces in MDX files
How we calculate
- Days between releases: The median of the gaps, in days, between the release dates listed above.
Data: tailwindlabs/tailwindcss's GitHub releases page, read November 18, 2026. Every other figure on this page is copied from the record, not calculated by us.
Get this for your repo, every release
tailwindcss publishes release notes that people can read. FoxPlug writes yours from what you ship: a changelog entry and posts for the places your users are, each approved by you.
Get this for your repo, every releaseTry it on your repo nowYour changelog, written for you
FoxPlug writes your changelog from your releases and commits in plain English and publishes it as a page and a feed your users can follow. The page above shows what that looks like for a product people really use.
Write my changelog See the changelog FoxPlug wrote from its own commits
Free to start. Pro is a month.
FoxPlug Pro
- A public changelog page and feed for each project
- Written from your releases and commits, in plain English your users read
- Connect GitHub and new releases become new entries