Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This has to be done before we update to django 4.2, because the references to the tagging app (which might get removed at all) are needed. Although this could be made simpler, imho, i decided to go the official django way and squash all migrations for the news. The advantage of this workflow is to have in the end only one migration file (instead of 4). This must be a two-step process with two separate PR's:
To get this in:
Merge this branch
run ./manage.py migrate