Django 5.1 testing, dropped Django 3.2 / Postgres 12 support #157
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wesleykendall
force-pushed
the
_footing_update
branch
from
62d3ad3 to
d12dad6
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Note that this primarily applies changes from the main python template. It does not yet incorporate fixes in #156, which is required for pgtrigger to be fully compatible.
This PR addresses #133 by removing git-tidy from the release process in favor of manually releasing via Github releases.
Will follow up on the full release for Django 5.1 compatibility in another PR and Github release of pgtrigger v4.12