Skip to content
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

Update tailwindcss 4.0.0 → 4.0.6 (patch) #1856

Closed
wants to merge 1 commit into from

Conversation

depfu[bot]
Copy link
Contributor

@depfu depfu bot commented Feb 11, 2025

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ tailwindcss (4.0.0 → 4.0.6) · Repo · Changelog

Release Notes

4.0.6

Fixed

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

4.0.5

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

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

Fixed

  • Fix incorrect removal of @import url(); (#16144)

4.0.2

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

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)

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by 70 commits:


Depfu Status

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands
@​depfu rebase
Rebases against your default branch and redoes this update
@​depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@​depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@​depfu cancel merge
Cancels automatic merging of this PR
@​depfu close
Closes this PR and deletes the branch
@​depfu reopen
Restores the branch and reopens this PR (if it's closed)
@​depfu pause
Ignores all future updates for this dependency and closes this PR
@​depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@​depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)

@depfu depfu bot added the depfu label Feb 11, 2025
Copy link

vercel bot commented Feb 11, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
lordronz-site ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 11, 2025 3:44pm

Copy link
Contributor Author

depfu bot commented Feb 14, 2025

Closing because this update has already been applied

@depfu depfu bot closed this Feb 14, 2025
@depfu depfu bot deleted the depfu/update/pnpm/tailwindcss-4.0.6 branch February 14, 2025 14:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants