Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump django-taggit from 1.5.1 to 5.0.1 #735

Closed
wants to merge 37 commits into from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Oct 30, 2023

Bumps django-taggit from 1.5.1 to 5.0.1.

Changelog

Sourced from django-taggit's changelog.

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 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 (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).
  • 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.

3.0.0 (2022-05-02)


* **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.

</tr></table>

... (truncated)

Commits
  • 9aaac8f Merge pull request #879 from jazzband/fix-readthedocs
  • e2cffd8 Properly bump the version number to 5.0.1
  • d04dcc3 Update the contributing doc to mention the docuemntation page as well
  • f18f166 Update the documentation for the Python and Django versions
  • ed7b5b4 install the project so that the version number is available
  • a6271f4 Point to the right version in Sphinx
  • 5425d20 Add a readthedocs configuration file
  • 1b241a3 Merge pull request #877 from jazzband/prepare-5-0-1
  • b5ded0d Prepare release 5.0.1
  • ccd0823 Update setup.cfg to properly describe the right minimum Django and Python ver...
  • Additional commits viewable in compare view

Dependabot compatibility score

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)

@dependabot @github
Copy link
Author

dependabot bot commented on behalf of github Oct 30, 2023

The following labels could not be found: dependencies.

Copy link
Author

dependabot bot commented on behalf of github Nov 4, 2024

Superseded by #885.

@dependabot dependabot bot closed this Nov 4, 2024
@dependabot dependabot bot deleted the dependabot/pip/django-taggit-5.0.1 branch November 4, 2024 09:40
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.

2 participants