Skip to content

Conversation

flavorjones
Copy link
Member

Now that we've done the work to be compatible with Tailwind v4 in a v4.0.0.rc1, I think we know enough to recommend against using Tailwind v4 with tailwindcss-rails v3.

Let's prevent unintentional upgrades and problems for users. This will go into a (final?) v3 release.

@flavorjones flavorjones changed the title dep: ping tailwindcss-ruby to ~> 3.0 dep: pin tailwindcss-ruby to ~> 3.0 Jan 23, 2025
to avoid unintentional upgrades to Tailwind v4
@flavorjones flavorjones force-pushed the flavorjones-v3-pin-to-tailwind-3 branch from cfb48a9 to 1f694ad Compare January 23, 2025 20:16
@flavorjones flavorjones merged commit 8b31d59 into v3-stable Jan 23, 2025
12 checks passed
@flavorjones flavorjones deleted the flavorjones-v3-pin-to-tailwind-3 branch January 23, 2025 20:30
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.

1 participant