Bump tailwindcss-rails from 3.3.0 to 4.0.0

[dependabot]

Bumps tailwindcss-rails from 3.3.0 to 4.0.0.

Release notes

Sourced from tailwindcss-rails's releases.

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

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

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

... (truncated)

Changelog

Sourced from tailwindcss-rails's changelog.

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

v3.3.1 / 2025-01-23

• Pin the dependency on tailwindcss-ruby to ~> 3.0 to prevent users from upgrading Tailwind 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.

Commits

• 3d87104 version bump to v4.0.0
• ecdbdee Merge pull request #485 from rails/flavorjones-prep-for-upgrade
• 0cc3f19 doc: further improvements to the README
• 976ddab doc: emit a post-install message with a pointer to upgrade docs
• e37ed78 doc: update README upgrade guide for css class names
• 738ba68 version bump to v4.0.0.rc5
• 3a5fedc Merge pull request #483 from patriciomacadden/hide-authentication-generator
• 43eeffd Hide tailwindcss:authentication from rails g
• 09e237e Merge pull request #482 from EricGusmao/update-postcss-path
• 51efc7f fix: update postcss config path to root directory
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)