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 dependency tailwindcss to v4 #2019

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

pulumi-renovate[bot]
Copy link
Contributor

@pulumi-renovate pulumi-renovate bot commented Feb 17, 2025

This PR contains the following updates:

Package Type Update Change
tailwindcss (source) dependencies major 3.4.17 -> 4.0.9

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

tailwindlabs/tailwindcss (tailwindcss)

v4.0.9

Compare Source

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)

v4.0.8

Compare Source

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

v4.0.7

Compare Source

Fixed
  • Export tailwindcss/lib/util/flattenColorPalette.js for backward compatibility (#​16411)
  • Fix sorting of numeric utility suggestions when they have different magnitudes (#​16414)
  • Show suggestions for fractions in IntelliSense (#​16353)
  • Don’t replace _ in suggested theme keys (#​16433)
  • Ensure --default-outline-width can be used to change the outline-width value of the outline utility (#​16469)
  • Ensure drop shadow utilities don't inherit unexpectedly (#​16471)
  • Export config and plugin types from tailwindcss/plugin for backward compatibility (#​16505)
  • Ensure JavaScript plugins that emit nested rules referencing the utility name work as expected (#​16539)
  • Statically link Visual Studio redistributables in @tailwindcss/oxide Windows builds (#​16602)
  • Ensure that Next.js splat routes are scanned for classes (#​16457)
  • Pin exact version of tailwindcss in @tailwindcss/* packages (#​16623)
  • Upgrade: Report errors when updating dependencies (#​16504)
  • Upgrade: Ensure a darkMode JS config setting with block syntax converts to use @slot (#​16507)
  • Upgrade: Ensure the latest version of tailwindcss and @tailwindcss/postcss are installed when upgrading (#​16620)

v4.0.6

Compare Source

Fixed
  • Revert change to no longer include theme variables that aren't used in compiled CSS (#​16403)
Fixed
  • Upgrade: Don't migrate blur to blur-sm when used with Next.js <Image placeholder="blur" /> (#​16405)

v4.0.5

Compare Source

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)

v4.0.4

Compare Source

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)

v4.0.3

Compare Source

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

v4.0.2

Compare Source

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)

v4.0.1

Compare Source

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)

v4.0.0

Compare Source

Added

Start using Tailwind CSS v4.0 today by installing it in a new project, or playing with it directly in the browser on Tailwind Play.

For existing projects, we've published a comprehensive upgrade guide and built an automated upgrade tool to get you on the latest version as quickly and painlessly as possible.

For a deep-dive into everything that's new, check out the announcement post.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "every weekday" (UTC).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@pulumi-renovate pulumi-renovate bot added dependencies Pull requests that update a dependency file impact/no-changelog-required This issue doesn't require a CHANGELOG update labels Feb 17, 2025
@pulumi-renovate pulumi-renovate bot enabled auto-merge (squash) February 17, 2025 16:33
@pulumi-renovate pulumi-renovate bot force-pushed the renovate/tailwindcss-4.x branch 12 times, most recently from 979ed03 to 333add5 Compare February 24, 2025 11:11
@pulumi-renovate pulumi-renovate bot force-pushed the renovate/tailwindcss-4.x branch from 333add5 to 6d0b735 Compare February 25, 2025 18:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file impact/no-changelog-required This issue doesn't require a CHANGELOG update
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants