Django-pg-migration-tools

Changed

- `migrate_with_timeouts` callbacks can now access the migration stdout via
`RetryState.stdout` and the time since the migration started with
`RetryState.time_since_start`.
- Added a new operation `SaferAddUniqueConstraint` that provides a way to
safely create unique constraints.

Changed

- `migrate_with_timeouts` will now raise `MaximumRetriesReached` instead of
`CommandError` when the maximum number of retries is reached.

Changed

- The implementation of `migrate_with_timeouts` now has additional flags to
perform retries:
bash
./manage.py migrate_with_timeouts \
--lock-timeout-in-ms=10000 \
--lock-timeout-max-retries=3 \
--lock-timeout-retry-exp=2 \
--lock-timeout-retry-min-wait-in-ms=3000 \
--lock-timeout-retry-max-wait-in-ms=10000 \
--statement-timeout-in-ms=10000 \
--retry-callback-path="dotted.path.to.callback.function"

Added

- `SaferRemoveIndexConcurrently` migration operation to drop Postgres indexes
in a safer way than Django's `RemoveIndexConcurrently`.

Changed

- The internal implementation for `SaferAddIndexConcurrently` has been changed
to inherit from Django's `AddIndexConcurrently` operation rather than
Django's `Operation` class. This means that the interface is now the same and
the "hints" argument is not valid any longer.

- Fixes a bug where the `SaferAddIndexConcurrently` class would try to perform
a migration regardless of whether the router would allow it (through
`router.allow_migrate`).

- Non-functional changes for the documentation to be properly linked in PyPI.