- TAILWIND_CLI_VERSION defaults to "latest" now. In case it is set to this value, django-tailwind-cli tries to determine which version is the latest version of Tailwind CSS. If it is not able to access the internet, it uses a fallback version defined in django_tailwind_cli.config.FALLBACK_VERSION. Currently, it is set to 4.0.6.
4.0.1
- Various fixes for the documentation. - Added Django 5.2 to the testing matrix.
4.0.0
- Added support for Tailwind CSS 4.0.0. - Default version is Tailwind CSS 4.0.0. - The versioning is now aligned with Tailwind CSS. That means the major number of this packages follows the major number of Tailwind CSS to document the most recent supported version of Tailwind. - Removed the management commands `install_pycharm_workaround` and `uninstall_pycharm_workaround`. This feature broke too often. - Removed `runserver_plus` subcommand. The management subcommand `runserver` now starts either the debug server from django-extensions if this package is installed. Otherwise it starts the standard debug server. - The management subcommand `runserver` got an option `--force-default-runserver` to enforce the usage of the standard debug server from Django. - `TAILWIND_CLI_CONFIG_FILE` isn't necessary for Tailwind CSS 4.x only for 3.x. [Read the documentaiton about it.](https://django-tailwind-cli.rtfd.io/latest/installation/settings) - Removed the documentation for the fancier `tailwind.config.js` as it is not recommended to use and Tailwind CSS 4.x has a way better strategy to find the used Tailwind classes.
2.21.1
- Relaxed the minimum Django version to >=4.0.
2.21.0
- Added `install_pycharm_workaround` and `remove_pycharm_workaround` management commands. [142](https://github.com/django-commons/django-tailwind-cli/issues/142) - Added `remove_cli` subcommand to remove the CLI. [132](https://github.com/django-commons/django-tailwind-cli/issues/132) - Refactored all the class based management command into simpler function based commands. - Refactored the process to build the runserver command.