Update tailwindcss-rails 3.3.2 → 4.3.0 (major)

[depfu]

Here is everything you need to know about this update. Please take a good look at what changed and the test results before merging this pull request.

What changed?

✳️ tailwindcss-rails (3.3.2 → 4.3.0) · Repo · Changelog

Release Notes

4.3.0

v4.3.0 / 2025-07-06

Improved

• Experimental support for Rails engines. Feedback is welcome at #355. #554, #556 @bopm
• Gracefully handle application created with --skip-system-test. #559, #562 @flavorjones

4.2.3

v4.2.3 / 2025-05-02

Improved

• The "tailwindcss:upgrade" task now pins to v4.1.4 of the @tailwindcss/upgrade tool. #544 @flavorjones

4.2.2

v4.2.2 / 2025-04-05

Improved

• The "tailwindcss:upgrade" task now uses the latest version of the @tailwindcss/upgrade tool. #529 @flavorjones
• The "verbose" flag on Rails tasks now emits additional tailwind CLI debugging info (e.g., bin/rails tailwindcss:build[verbose]). #530 @flavorjones
• Simplified the scaffold templates, removing unnecessary div tags. @523 @patriciomacadden

4.2.1

v4.2.1 / 2025-03-19

Fixed

• Fix styles for form errors in some scaffold fields. #513 @patriciomacadden
• Update scaffold system tests to handle the "Destroy" confirmation prompt when Turbo is enabled. Fixes #519. #520 @patriciomacadden @flavorjones

4.2.0

v4.2.0 / 2025-03-02

Features

• Improve the view templates to display better on mobile devices. #503 @patriciomacadden
• Support for environment variable TAILWINDCSS_DEBUG to turn off CSS minification. #504 @r-sierra

4.1.0

v4.1.0 / 2025-02-19

View template improvements

• Field outlines are no longer hidden, and the focus border is brighter. #489 @rubys
• Boolean fields are improved (checkbox labels aligned, "Yes"/"No" instead of "true"/"false"). #454 @patriciomacadden
• Attachment links are consistently spaced and styled. #460 @patriciomacadden
• Index page links to Show, Edit, and Destroy for each resource. #460 @patriciomacadden @flavorjones
• Turbo confirm prompt added to Destroy links. #498 @patriciomacadden

4.0.0

v4.0.0 / 2025-02-01

Upgrade to Tailwind CSS v4

General changes:

• The dependency on tailwindcss-ruby is set to ~> 4.0.
• The location of (optional) postcss.config.js has moved from the config/ directory to the app root.
• The input file app/assets/tailwind/application.tailwind.css has been renamed to app/assets/tailwind/application.css.
• If Propshaft is being used, app/assets/tailwind will be excluded from its asset handling.
• The Inter font is no longer packaged with the gem.
• Some Tailwind class names in the generated ERB templates are updated for v4.
• The README is updated to contain verbose instructions on upgrading.

Changes to the tailwindcss:install task:

• The tailwindcss:install task no longer installs config/tailwind.config.js, as v4 recommends placing Tailwind configuration in the CSS file.
• The Inter font is no longer configured in the application layout.
• The "tailwind" stylesheet link tag will only be added to the application layout if Propshaft isn't in use and therefore already handling app/assets/build/tailwind.css. Previously it was always injected, resulting in the tag being rendered twice if Propshaft was in use.

New task tailwindcss:upgrade upgrades many apps cleanly:

• Cleans up config/tailwind.config.js and references it from the CSS file as recommended for v4 upgrades.
• Runs the upstream upgrader (note: requires npx to run the one-time upgrade, but highly recommended).
• Removes configuration for the Inter font from the application layout.
• If present, moves config/postcss.config.js to the root directory.
• The "tailwind" stylesheet link tag will be removed if Propshaft is in use and already handling app/assets/build/tailwind.css.
• The input file app/assets/tailwind/application.tailwind.css will be moved to app/assets/tailwind/application.css.

Thanks to @EricGusmao, @patriciomacadden, @excid3, and @brunoprietog for their feedback, contributions, and advice on v4 support.

Other changes

• The gem's Rails generators are now hidden in the rails g --help output. #483 @patriciomacadden

Does any of this look wrong? Please let us know.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

↗️ tailwindcss-ruby (indirect, 3.4.17 → 4.1.11) · Repo · Changelog

Release Notes

Too many releases to show here. View the full release notes.

Commits

See the full diff on Github. The new version differs by more commits than we can show here.

---

Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.

All Depfu comment commands

@​depfu rebase

Rebases against your default branch and redoes this update

@​depfu recreate

Recreates this PR, overwriting any edits that you've made to it

@​depfu merge

Merges this PR once your tests are passing and conflicts are resolved

@​depfu cancel merge

Cancels automatic merging of this PR

@​depfu close

Closes this PR and deletes the branch

@​depfu reopen

Restores the branch and reopens this PR (if it's closed)

@​depfu pause

Ignores all future updates for this dependency and closes this PR

@​depfu pause [minor|major]

Ignores all future minor/major updates for this dependency and closes this PR

@​depfu resume

Future versions of this dependency will create PRs again (leaves this PR as is)

Go to the Depfu Dashboard to see the state of your dependencies and to customize how Depfu works.

[depfu]

Closed in favor of #837.