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

Bump tailwindcss from 3.4.17 to 4.0.8 #1065

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

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 21, 2025

Bumps tailwindcss from 3.4.17 to 4.0.8.

Release notes

Sourced from tailwindcss's releases.

v4.0.8

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

  • Don't include theme variables that aren't used in compiled CSS (#16211, #16676)

v4.0.7

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

Fixed

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

v4.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)

... (truncated)

Changelog

Sourced from tailwindcss's changelog.

[4.0.8] - 2025-02-21

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

  • Don't include theme variables that aren't used in compiled CSS (#16211, #16676)

[4.0.7] - 2025-02-18

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)

[4.0.6] - 2025-02-10

Fixed

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

[4.0.5] - 2025-02-08

Added

... (truncated)

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

@dependabot dependabot bot added the dependencies Updates a dependency label Feb 21, 2025
@dependabot dependabot bot requested a review from ahmadk953 February 21, 2025 17:55
Copy link

vercel bot commented Feb 21, 2025

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

Name Status Preview Comments Updated (UTC)
tasko ❌ Failed (Inspect) Feb 21, 2025 8:56pm

Copy link

coderabbitai bot commented Feb 21, 2025

Important

Review skipped

Ignore keyword(s) in the title.

⛔ Ignored keywords (1)
  • Bump

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

codecov bot commented Feb 21, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 91.44%. Comparing base (1eea76a) to head (20c2619).

✅ All tests successful. No failed tests found.

Additional details and impacted files
@@           Coverage Diff           @@
##             main    #1065   +/-   ##
=======================================
  Coverage   91.44%   91.44%           
=======================================
  Files          17       17           
  Lines         947      947           
  Branches       44       44           
=======================================
  Hits          866      866           
  Misses         81       81           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

codecov bot commented Feb 21, 2025

Bundle Report

Changes will decrease total bundle size by 41.59kB (-0.27%) ⬇️. This is within the configured threshold ✅

Detailed changes
Bundle name Size Change
nextjs-webpack-bundle-server-cjs 9.03MB 35 bytes (0.0%) ⬆️
nextjs-webpack-bundle-edge-server-array-push 2.96MB 11 bytes (0.0%) ⬆️
nextjs-webpack-bundle-client-array-push 3.22MB -41.64kB (-1.28%) ⬇️

Affected Assets, Files, and Routes:

view changes for bundle: nextjs-webpack-bundle-edge-server-array-push

Assets Changed:

Asset Name Size Change Total Size Change (%)
middleware.js 11 bytes 365.52kB 0.0%
view changes for bundle: nextjs-webpack-bundle-client-array-push

Assets Changed:

Asset Name Size Change Total Size Change (%)
static/chunks/9100-*.js -3 bytes 476.86kB -0.0%
static/chunks/pages/_app-*.js -3 bytes 292.7kB -0.0%
static/chunks/app/layout-*.js 10.29kB 20.61kB 99.72% ⚠️
static/chunks/584-*.js 22 bytes 10.79kB 0.2%
static/css/*.css -51.95kB 2.06kB -96.18%
static/chunks/webpack-*.js -2 bytes 3.88kB -0.05%
static/L1J0JkR9o1edHn6HO8Uh6/_buildManifest.js (New) 1.23kB 1.23kB 100.0% 🚀
server/middleware-*.js 584 bytes 955 bytes 157.41% ⚠️
server/middleware-*.js -584 bytes 371 bytes -61.15%
static/L1J0JkR9o1edHn6HO8Uh6/_ssgManifest.js (New) 77 bytes 77 bytes 100.0% 🚀
static/1Zl88vuaF4MoeOW12AvT9/_buildManifest.js (Deleted) -1.23kB 0 bytes -100.0% 🗑️
static/1Zl88vuaF4MoeOW12AvT9/_ssgManifest.js (Deleted) -77 bytes 0 bytes -100.0% 🗑️

App Routes Affected:

App Route Size Change Total Size Change (%)
/ 10.29kB 27.74kB 58.98% ⚠️
view changes for bundle: nextjs-webpack-bundle-server-cjs

Assets Changed:

Asset Name Size Change Total Size Change (%)
292.js -3 bytes 991.02kB -0.0%
29.js -3 bytes 926.64kB -0.0%
356.js 33 bytes 859.5kB 0.0%
../instrumentation.js -3 bytes 827.51kB -0.0%
84.js 11 bytes 87.94kB 0.01%

Bumps [tailwindcss](https://github.com/tailwindlabs/tailwindcss/tree/HEAD/packages/tailwindcss) from 3.4.17 to 4.0.8.
- [Release notes](https://github.com/tailwindlabs/tailwindcss/releases)
- [Changelog](https://github.com/tailwindlabs/tailwindcss/blob/main/CHANGELOG.md)
- [Commits](https://github.com/tailwindlabs/tailwindcss/commits/v4.0.8/packages/tailwindcss)

---
updated-dependencies:
- dependency-name: tailwindcss
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot force-pushed the dependabot/npm_and_yarn/tailwindcss-4.0.8 branch from 04189e9 to 20c2619 Compare February 21, 2025 20:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Updates a dependency
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant