Skip to content

Update django-taggit to 5.0.0 - #169

Closed
pyup-bot wants to merge 1 commit into
masterfrom
pyup-update-django-taggit-3.1.0-to-5.0.0
Closed

Update django-taggit to 5.0.0#169
pyup-bot wants to merge 1 commit into
masterfrom
pyup-update-django-taggit-3.1.0-to-5.0.0

Conversation

@pyup-bot

Copy link
Copy Markdown
Collaborator

This PR updates django-taggit from 3.1.0 to 5.0.0.

Changelog

5.0.0

~~~~~~~~~~~~~~~~~~
* **Backwards icompatible:** Rename the (``content_type``, ``object_id``) index on ``TaggedItem``.
It is very unlikely for this to affect your code itself, and a migration will rename the index. This should not cause any downtime according to my research (Postgres does not lock the table for index renames, and Oracle holds a tiny lock to do it, and the change is only to the metadata, so is not dependent on table size).

* **Backwards incompatible:** Remove the ``.indexed_together`` and ``.unique_together`` attributes on ``TaggedItem``

We are instead using ``constraints`` and ``indexes`` to set up these properties.
* Remove support for Django 3.2.
* Remove usage of deprecated APIs for Django 4.2
* Remove support for Python 3.7 (no code changes involved)
* Fix ``tag_kwargs`` and ``TAGGIT_CASE_INSENSITIVE=True`` discrepency.

4.0.0

~~~~~~~~~~~~~~~~~~
* Remove Python 3.6 support (no code changes occurred, but we no longer test this release).
* Remove Django 4.0 support (no code changes occurred, but we no longer test this release).
* Add Django 4.2 support.
Links

@pyup-bot

Copy link
Copy Markdown
Collaborator Author

Closing this in favor of #170

@pyup-bot pyup-bot closed this Oct 29, 2023
@rogeriodelphi
rogeriodelphi deleted the pyup-update-django-taggit-3.1.0-to-5.0.0 branch October 29, 2023 13:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant