v4.0.0 / 2025-02-01

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

v4.0.0.rc5 / 2025-01-29

v4.0.0.rc5 / 2025-01-29

General changes since rc4:

• Update the rake tasks to detect an (optional) postcss file in the root directory, after moving the file in #466. #482 @EricGusmao
• Hide the gem's Rails generators in the rails g --help output. #483 @patriciomacadden

v4.0.0.rc4 / 2025-01-27

v4.0.0.rc4 / 2025-01-27

Everything in v4.0.0.rc3 plus ...

• The input file app/assets/tailwind/application.tailwind.css has been renamed to app/assets/tailwind/application.css.
• Updated README docs on using the upgrade tool to update class names. @EricGusmao

v4.0.0.rc3 / 2025-01-27

v4.0.0.rc3 / 2025-01-27

Everything in v4.0.0.rc2, plus ...

General changes:

• Remove the Inter font assets from the gem. @EricGusmao
• If Propshaft is being used, app/assets/tailwind will be excluded from its asset handling. (This was incompletely fixed in RC2.)

v4.0.0.rc2 / 2025-01-26

v4.0.0.rc2 / 2025-01-26

Changes since v4.0.0.rc1

General changes:

• The location of application.tailwind.css has moved from app/assets/stylesheets to app/assets/tailwind. If Propshaft is being used, app/assets/tailwind will be excluded from its asset handling.

Changes to the tailwindcss:install task:

• The "tailwind" stylesheet link tag will only be added to the application layout if Propshaft isn't in use and already handling app/assets/build/tailwind.css. Previously it was always injected, resulting in the tag being rendered twice if Propshaft was in use.

Changes to the tailwindcss:upgrade task:

• The "tailwind" stylesheet link tag will be removed if Propshaft is in use and already handling app/assets/build/tailwind.css.
• The file application.tailwind.css will be moved from app/assets/stylesheets to app/assets/tailwind.

Contributors

• @EricGusmao made their first contribution in #476
• Thanks to @patriciomacadden for #469

v4.0.0.rc1 / 2025-01-23

v4.0.0.rc1 / 2025-01-23

Upgrade to Tailwind CSS v4

Upgrade guide is in the README.

General changes:

• Dependency on tailwindcss-ruby set to ~> 4.0.
• The location of (optional) postcss.config.js has moved from the config/ directory to the app root.

Changes to the tailwindcss:install task:

• The tailwindcss:install task no longer installs config/tailwind.config.js.
• The Inter font is no longer packaged with the gem.
• Some Tailwind class names are updated for v4.

New task tailwindcss:upgrade upgrades many apps cleanly:

• Cleans up some things in the generated config/tailwind.config.js.
• Runs the upstream upgrader (note: requires npx to run the one-time upgrade, but highly recommended).
• Removes references to the Inter font from the application layout.
• If present, moves config/postcss.config.js to the root directory.

Thanks to @EricGusmao and @excid3 for their help and advice on this work.

v3.3.1 / 2025-01-23

v3.3.1 / 2025-01-23

• Pin the dependency on tailwindcss-ruby to ~> 3.0 to prevent users from upgrading Tailwind to v4 while still on v3 of this gem.

  While it was useful during the Tailwind v4 beta period to allow users to float this dependency to try upgrading, we know (now that v4.0.0.rc1 of this gem is out) that not everything will work well if combining Tailwind v4 with tailwindcss-rails v3. Pinning this dependency should protect developers against unexpected issues.

v3.3.0 / 2025-01-19

v3.3.0 / 2025-01-19

• Add support for using the puma plugin in a standalone puma process (outside of rails server). (#458) @flavorjones

v3.2.0 / 2025-01-10

v3.2.0 / 2025-01-10

• Improve the scaffold views by making positions, padding, and sizes more consistent, add titles to all pages, add hover states and semantic colors to buttons and links, and change border and focus colors on fields with errors. (#452) @patriciomacadden

New Contributors

• @patriciomacadden made their first contribution in #452

Full Changelog: v3.1.0...v3.2.0

v3.1.0 / 2024-12-29

v3.1.0 / 2024-12-29

Notable changes

The tailwindcss plugins "form", "typography", and "container-queries" have been dropped from the default generated tailwind.config.js file. If you'd like to use them, you can re-add them to your project by uncommenting the appropriate lines in your config file. (#446) @flavorjones