Skip to content

Conversation

@philipp-spiess
Copy link
Member

In some local testing we ran the @tailwindcss/upgrade command twice in a row. It would be great to get some feedback that this is not working, so this PR now checks if it can resolve the installed version of tailwindcss and if it can, it requires it to be < 4 (you can bypass this check with --force).

@philipp-spiess philipp-spiess requested a review from a team as a code owner November 15, 2024 17:05
@philipp-spiess philipp-spiess force-pushed the feat/check-tw-version-before-upgrade branch from f942429 to 194f4f2 Compare November 18, 2024 09:33
Copy link
Member

@RobinMalfait RobinMalfait left a comment

Choose a reason for hiding this comment

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

Also needs a changelog entry

@RobinMalfait RobinMalfait force-pushed the feat/check-tw-version-before-upgrade branch from 1d716c4 to 71ce1fa Compare November 18, 2024 16:49
@RobinMalfait RobinMalfait merged commit b3d1cbb into next Nov 19, 2024
1 check passed
@RobinMalfait RobinMalfait deleted the feat/check-tw-version-before-upgrade branch November 19, 2024 14:53
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.

3 participants