- Published on
Release: pgtrigger migrations & codegen formatting
- Authors
- Name
- Dave Coates
This release contains changes up until release/2022-09-13.
To upgrade any existing projects it's recommended to pull in the relevant commits from upstream.
git remote add upstream git@gitlab.internal.alliancesoftware.com.au:alliance/template-django.git
git cherry-pick XXX1 XXX2
In cases where you are significantly behind it may be easier to pull the whole app (eg. common_audit) in but you'll
need to review the relevant branch.
In this release
pgtrigger migrations
Since the release of pgtrigger 3 migrations are now used to manage
triggers rather than a command that is automatically run after migrations. To upgrade see the original MR.
Note that when you upgrade you may need to manually run a prune the first time the migrations are deployed to cleanup
pre-migration triggers. See point 3 under the upgrade notes.
This change means the following are no longer necessary and have been removed
- check_migrations_drop_trigger_before_alter_table
- AuditTriggers / InstallTriggers / DropTriggers
- pgconnection
Codegen lint compatibility
Codegen previously didn't necessarily sort imports or comply with our flake8 settings and sometimes included unused imports. This has been resolved which means code generated files can be committed without first reformatting.
As a reminder it's generally preferred to run codegen and then immediately commit the code generated files before making changes. This makes it easier for reviewers - they can skip the generic code and focus on the changes specific to the use case.
See this MR for the commits necessary to upgrade.
Presto 0.0.33
Minor fix here for pagination when used with React 18. Any project that upgraded to React 18 should upgrade.