[Snyk] Upgrade tailwindcss from 3.3.3 to 3.4.6

[ZeroXClem]

Snyk has created this PR to upgrade tailwindcss from 3.3.3 to 3.4.6.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 11 versions ahead of your current version.

• The recommended version was released on a month ago.

Release notes

Package name: tailwindcss

• 3.4.6 - 2024-07-16
  

  Fixed

  • Fix detection of some utilities in Slim/Pug templates (#14006)

  Changed

  • Loosen :is() wrapping rules when using an important selector (#13900)
• 3.4.5 - 2024-07-15
  

  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)
• 3.4.4 - 2024-06-05
  

  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)
• 3.4.3 - 2024-03-27
  

  Fixed

  • Revert changes to glob handling (#13384)
• 3.4.2 - 2024-03-27
  

  Fixed

  • Ensure max specificity of 0,0,1 for button and input Preflight rules (#12735)
  • Improve glob handling for folders with (, ), [ or ] in the file path (#12715)
  • Split :has rules when using experimental.optimizeUniversalDefaults (#12736)
  • Sort arbitrary properties alphabetically across multiple class lists (#12911)
  • Add mix-blend-plus-darker utility (#12923)
  • Ensure dashes are allowed in variant modifiers (#13303)
  • Fix crash showing completions in Intellisense when using a custom separator (#13306)
  • Transpile import.meta.url in config files (#13322)
  • Reset letter spacing for form elements (#13150)
  • Fix missing xx-large and remove double x-large absolute size (#13324)
  • Don't error when encountering nested CSS unless trying to @ apply a class that uses nesting (#13325)
  • Ensure that arbitrary properties respect important configuration (#13353)
  • Change dark mode selector so @ apply works correctly with pseudo elements (#13379)
• 3.4.1 - 2024-01-05
  

  Fixed

  • Don't remove keyframe stops when using important utilities (#12639)
  • Don't add spaces to gradients and grid track names when followed by calc() (#12704)
  • Restore old behavior for class dark mode strategy (#12717)

  Added

  • Add new selector and variant strategies for dark mode (#12717)

  Changed

  • Support rtl and ltr variants on same element as dir attribute (#12717)
• 3.4.0 - 2023-12-19
  

  

  Tailwind CSS v3.4 has arrived! Check out the announcement post for a guided tour through all of the highlights.

  Added

  • Add svh, lvh, and dvh values to default height/min-height/max-height theme (#11317)
  • Add has-* variants for :has(...) pseudo-class (#11318)
  • Add text-wrap utilities including text-balance and text-pretty (#11320, #12031)
  • Extend default opacity scale to include all steps of 5 (#11832)
  • Update Preflight html styles to include shadow DOM :host pseudo-class (#11200)
  • Increase default values for grid-rows-* utilities from 1–6 to 1–12 (#12180)
  • Add size-* utilities (#12287)
  • Add utilities for CSS subgrid (#12298)
  • Add spacing scale to min-w-*, min-h-*, and max-w-* utilities (#12300)
  • Add forced-color-adjust utilities (#11931)
  • Add forced-colors variant (#11694, #12582)
  • Add appearance-auto utility (#12404)
  • Add logical property values for float and clear utilities (#12480)
  • Add * variant for targeting direct children (#12551)

  Changed

  • Simplify the sans font-family stack (#11748)
  • Disable the tap highlight overlay on iOS (#12299)
  • Improve relative precedence of rtl, ltr, forced-colors, and dark variants (#12584)
• 3.3.7 - 2023-12-18
• 3.3.6 - 2023-12-04
• 3.3.5 - 2023-10-25
• 3.3.4 - 2023-10-24
• 3.3.3 - 2023-07-13

from tailwindcss GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

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

• X
• Mastodon
• Reddit
• LinkedIn

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>.
  • 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 generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @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 as 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 resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

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.