[deps] Update django-taggit requirement from ~=4.0.0 to ~=6.1.0
Updates the requirements on django-taggit to permit the latest version.
Changelog
Sourced from django-taggit's changelog.
6.1.0 (2024-09-29)
* Add a management command (``remove_orphaned_tags``) to remove orphaned tags * Add a fallback for when multiple tags are found in case-insensitivity mode (the earliest by PK is returned) * Add a ``deduplicate_tags`` management command to remove duplicate tags based on case insensitivity. This feature is enabled when ``TAGGIT_CASE_INSENSITIVE`` is set to ``True`` in the settings. * We no longer package tests, docs, or the sample taggit app into the distributed wheels. While we believe this shouldn't affect anything for users of the library, please tell us if you find yourself hitting issues (like around import errors) * Fix missing template file for admin merge tag action6.0.0 (2024-07-27)
- By default, order tag items on instances by the primary key. This generally means that they will be ordered by "creation date" for the tag item. The previous behavior for this was that by default tag items were not ordered. In practice tag items often end up ordered by creation date anyways, just due to how databases work, but this was not a guarantee. If you wish to have the old behavior, set
ordering=[]to yourTaggableManagerinstance. We believe that this should not cause a noticable performance change, and the number of queries involved should not change.- Added the ability to merge tags via the admin
- Add Django 5.0 support (no code changes were needed, but now we test this release).
- Add Python 3.12 support
- Add support for dumpdata/loaddata using natural keys
5.0.1 (2023-10-26)
* Fix the package metadata to properly reflect the right Django and Python version requirements Release 5.0.0 improperly stated its Django bounds as >=3.2, so people installing without bounds will end up on a version that won't work.5.0.0 (2023-10-24)
Backwards icompatible: Rename the (
content_type,object_id) index onTaggedItem. 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
.index_togetherand.unique_togetherattributes onTaggedItemWe are instead using
constraintsandindexesto 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_kwargsandTAGGIT_CASE_INSENSITIVE=Truediscrepency.4.0.0 (2023-05-04)
* 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.3.1.0 (2022-11-08)
- Add Python 3.11 support (no code changes were needed, but now we test this release).
... (truncated)
Commits
4e5f7deMerge pull request #922 from jazzband/6-1-01535f06Fix missing template file in packaging4f3ec30Merge pull request #921 from jazzband/prepare-6-1-00436236Prepare django-taggit 6.1.00cd1f24Merge pull request #914 from fazeelghafoor/feat/resolve-duplicate-tags0e3c865Merge remote-tracking branch 'origin/master' into feat/resolve-duplicate-tagsf4effb2Remove unused importe851a84Simplify deduplication management command0e10963sort imports150c025Make sure ordering is always by pk for handling multiples- Additional commits viewable in compare view
You can trigger a rebase of this PR by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot mergewill merge this PR after your CI passes on it@dependabot squash and mergewill squash and merge this PR after your CI passes on it@dependabot cancel mergewill cancel a previously requested merge and block automerging@dependabot reopenwill reopen this PR if it is closed@dependabot closewill close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill 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 versionwill 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 dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
Note Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
@dependabot recreate