Skip to content

chore(deps): update dependency tailwindcss to v4 #23

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

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

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 30, 2025

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
tailwindcss (source) ^3.4.0 -> ^4.0.0 age adoption passing confidence

Release Notes

tailwindlabs/tailwindcss (tailwindcss)

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.

v3.4.17

Compare Source

Fixed

v3.4.16

Compare Source

Fixed
  • Ensure the TypeScript types for PluginsConfig allow undefined values (#​14668)

Changed

v3.4.15

Compare Source

  • Bump versions for security vulnerabilities (#​14697)
  • Ensure the TypeScript types for the boxShadow theme configuration allows arrays (#​14856)
  • Set fallback for opacity variables to ensure setting colors with the selection:* variant works in Chrome 131 (#​15003)

v3.4.14

Compare Source

Fixed
  • Don't set display: none on elements that use hidden="until-found" (#​14625)

v3.4.13

Compare Source

Fixed
  • Improve source glob verification performance (#​14481)

v3.4.12

Compare Source

Fixed
  • Ensure using @apply with utilities that use @defaults works with rules defined in the base layer when using optimizeUniversalDefaults (#​14427)

v3.4.11

Compare Source

Fixed
  • Allow anchor-size(…) in arbitrary values (#​14393)

v3.4.10

Compare Source

Fixed
  • Bump versions of plugins in the Standalone CLI (#​14185)

v3.4.9

Compare Source

Fixed
  • No longer warns when broad glob patterns are detecting vendor folders

v3.4.8

Compare Source

Fixed
  • Fix minification when using nested CSS (#​14105)
  • Warn when broad glob patterns are used in the content configuration (#​14140)

v3.4.7

Compare Source

Fixed
  • Fix class detection in Slim templates with attached attributes and ID (#​14019)
  • Ensure attribute values in data-* and aria-* modifiers are always quoted in the generated CSS (#​14037)

v3.4.6

Compare Source

Fixed
  • Fix detection of some utilities in Slim/Pug templates (#​14006)
Changed
  • Loosen :is() wrapping rules when using an important selector (#​13900)

v3.4.5

Compare Source

Fixed
  • Disable automatic var() injection for anchor properties (#​13826)
  • Use no value instead of blur(0px) for backdrop-blur-none and blur-none utilities (#​13830)
  • Add .mts and .cts config file detection (#​13940)
  • Don't generate utilities like px-1 unnecessarily when using utilities like px-1.5 (#​13959)
  • Always generate -webkit-backdrop-filter for backdrop-* utilities (#​13997)

v3.4.4

Compare Source

Fixed
  • Make it possible to use multiple <alpha-value> placeholders in a single color definition (#​13740)
  • Don't prefix classes in arbitrary values of has-*, group-has-*, and peer-has-* variants (#​13770)
  • Support negative values for {col,row}-{start,end} utilities (#​13781)
  • Update embedded browserslist database (#​13792)

Configuration

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

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

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 was generated by Mend Renovate. View the repository job log.

Copy link

cloudflare-workers-and-pages bot commented Jan 30, 2025

Deploying website-v2 with  Cloudflare Pages  Cloudflare Pages

Latest commit: 2f589f2
Status:🚫  Build failed.

View logs

Copy link
Contributor Author

renovate bot commented Jan 30, 2025

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm warn Unknown env config "store". This will stop working in the next major version of npm.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: @astrojs/[email protected]
npm error Found: [email protected]
npm error node_modules/tailwindcss
npm error   dev tailwindcss@"^4.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer tailwindcss@"^3.0.24" from @astrojs/[email protected]
npm error node_modules/@astrojs/tailwind
npm error   dev @astrojs/tailwind@"^5.0.4" from the root project
npm error
npm error Conflicting peer dependency: [email protected]
npm error node_modules/tailwindcss
npm error   peer tailwindcss@"^3.0.24" from @astrojs/[email protected]
npm error   node_modules/@astrojs/tailwind
npm error     dev @astrojs/tailwind@"^5.0.4" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2025-04-15T19_07_24_543Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2025-04-15T19_07_24_543Z-debug-0.log

@renovate renovate bot force-pushed the renovate/major-tailwindcss-monorepo branch from 26d0fd3 to 2f589f2 Compare April 15, 2025 19:07
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.

0 participants