Skip to content

chore(deps): update tailwindcss to v4 #1760

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

Closed
wants to merge 1 commit into from
Closed

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Jan 23, 2025

This PR contains the following updates:

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

Release Notes

tailwindlabs/tailwindcss (tailwindcss)

v4.0.0

Compare Source

[4.0.0] - 2025-01-21


Configuration

📅 Schedule: Branch creation - "* 0-3 * * 1" (UTC), 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.

@renovate renovate bot added the dependency Dependency updates label Jan 23, 2025
@renovate renovate bot force-pushed the renovate/tailwindcss-4.x branch from a655ca2 to c28b3e0 Compare January 23, 2025 16:42
@bmulholland
Copy link
Collaborator

bmulholland commented Jan 24, 2025

I just shipped a v4 upgrade for work. The migration script is pretty good; it missed a few edge cases, but the process was relatively painless. There were a few visual regressions caused by legit issues (like logic that accidentally overlapped in some cases, adding two different height/width values).

Gitify doesn't have visual regression set up so there's a little risk with this upgrade, I guess.

I'd suggest just run Tailwind's npx upgrade, checking the diffs manually, and then just shipping it.

@setchy
Copy link
Member

setchy commented Jan 24, 2025

@bmulholland would you like to help with this one?

@bmulholland
Copy link
Collaborator

I'm pretty heavily time limited these days, but I'll give it a shot right now

@bmulholland
Copy link
Collaborator

Superseded by #1771

Copy link
Contributor Author

renovate bot commented Jan 24, 2025

Renovate Ignore Notification

Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for any future 4.x releases. But if you manually upgrade to 4.x then Renovate will re-enable minor and patch updates automatically.

If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

@renovate renovate bot deleted the renovate/tailwindcss-4.x branch January 24, 2025 11:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency Dependency updates
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants