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

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

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.3 -> ^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.


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

sourcery-ai bot commented Jan 30, 2025

Reviewer's Guide by Sourcery

This pull request updates the TailwindCSS dependency from version 3.4.3 to 4.0.0. The changes are primarily in the package.json and pnpm-lock.yaml files, reflecting the new version of TailwindCSS. This update includes various performance improvements and new features as outlined in the TailwindCSS v4.0.0 release notes.

No diagrams generated as the changes look simple and do not need a visual representation.

File-Level Changes

Change Details Files
Updated TailwindCSS dependency to version 4.0.0
  • Changed TailwindCSS version from 3.4.3 to 4.0.0 in package.json
  • Updated TailwindCSS version references in pnpm-lock.yaml
package.json
pnpm-lock.yaml

Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!
  • Generate a plan of action for an issue: Comment @sourcery-ai plan on
    an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

Copy link

@sourcery-ai sourcery-ai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, renovate[bot]!). We assume it knows what it's doing!

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