Django-tag-fields

Feature
* **tags:** Rename models ready for adding fields 66 ([`a21fec8`](https://github.com/imAsparky/django-tag-fields/commit/a21fec833f4745682228260e8f77886c0b8ddfd3))

Fix
* **ver:** Update conf.py location in sem_ver 68 ([`14ff854`](https://github.com/imAsparky/django-tag-fields/commit/14ff8549930c0c46a5ed097f92d61a36f5f281ed))

Documentation
* **models:** Update model names 66 ([`de364b4`](https://github.com/imAsparky/django-tag-fields/commit/de364b48ecf9afe09279b2c9d74f9f3fd7004c09))
* **structure:** Update to standard Sphinx 63 ([`f03086a`](https://github.com/imAsparky/django-tag-fields/commit/f03086acd78a8ad5d0af36dfb122e09444865ab0))
* **config:** Add readthedocs and extra deps 63 ([`94e4374`](https://github.com/imAsparky/django-tag-fields/commit/94e437496323dd5545d9ccd1f6b768fd653e9db5))
* **deps:** Update docutils 61 ([`c5a4ed3`](https://github.com/imAsparky/django-tag-fields/commit/c5a4ed3802cd421d2dab2d22a4fe814fb6305acd))

Fix
* **settings:** Update Constant names 59 ([`c2a9b3a`](https://github.com/imAsparky/django-tag-fields/commit/c2a9b3ab5047023464ff4a032f2eafce68c7d06b))

Documentation
* **settings:** Update Constant names 59 ([`1395043`](https://github.com/imAsparky/django-tag-fields/commit/13950430a4300365259f5e99c560f70c29069fca))
* **manager:** Add docstrings to select areas 57 ([`d524d44`](https://github.com/imAsparky/django-tag-fields/commit/d524d44ba99f4214ba05080903997593d6c6849f))
* **changelog:** Change .rst to .md 55 ([`5b5b6d9`](https://github.com/imAsparky/django-tag-fields/commit/5b5b6d9414a801cf9888440a9b388157fe164ad9))
* **typo:** Improve wording and layout 53 ([`0970e28`](https://github.com/imAsparky/django-tag-fields/commit/0970e28d52e37a6c25962c3a6d000bd857306281))

Fix
* **dev:** Add pre-commit to requirements 51 ([`5a27789`](https://github.com/imAsparky/django-tag-fields/commit/5a277893dd2b112fb57ac439c44c04b3f3e3183e))

Documentation
* **all:** Update with all model changes 38 ([`0efc84b`](https://github.com/imAsparky/django-tag-fields/commit/0efc84b6b16789990a097318e58ffa92c44bf413))

~~~~~~~~~~~~~~~~~~
* Initial release of django-tag-fields.
* A renaming of cloned `django-taggit`

This release functions the same as `django-taggit v3.1.0`. The changes here are simply
getting the project to be `django-tag-fields`, with all the necessary downstream changes
of renaming.

~~~~~~~~~~~~~~~~~~

* Add Python 3.11 support (no code changes were needed, but now we test this release).
* Add Django 4.1 support (no code changes were needed, but now we test this release).
* Fixed an issue where object caches would not be properly cleared after updating tags, leading
to stale reads in cases where ``prefetch_related`` is used.
* Change ``TagListSerializerField`` to be a subclass of ``ListField``. This should improve support for API document generation. This change should not affect API behavior, but might affect metaprogramming code, so please procede carefully during this update.

~~~~~~~~~~~~~~~~~~

* **Backwards incompatible:** Tag slugification used to silently strip non-ASCII characters
from the tag name to make the slug. This leads to a lot of confusion for anyone using
languages with non-latin alphabets, as well as weird performance issues.

Tag slugification will now, by default, maintain unicode characters as-is during
slugification. This will lead to less surprises, but might cause issues for you if you are
expecting all of your tag slugs to fit within a regex like ``[a-zA-Z0-9]`` (for example in
URL routing configurations).

Generally speaking, this should not require action on your part as a library user, as
existing tag slugs are persisted in the database, and only new tags will receive the
enhanced unicode-compatible slug.

If you wish to maintain the old stripping behavior, set the setting
``TAGS_STRIP_UNICODE_WHEN_SLUGIFYING`` to ``True``.

As a reminder, custom tag models can easily customize slugification behavior by overriding
the ``slugify`` method to your business needs.

`` Drop Django 2.2 support.