Django-subscriptions

Latest version: v2.1.1

Safety actively analyzes 623465 Python packages for vulnerabilities to keep your Python projects secure.

Scan your dependencies

Page 1 of 2

2.1.1

- Subscriptions in `SUSPENDED` state can now be `renewed()` which solves an issue
with payment callbacks correctly identifying a payment success.

2.1.0

- Introduced a boolean setting `SUBSCRIPTIONS_STUCK_RETRY`, defaulting to `False`, that will
cause stuck subscriptions to be marked as `renewal_failed` rather than `state_unknown`.

2.0.0

- Dropped support for Django < 2.2
- Dropped support for Python 2
- Made dependencies >= rather than ^ to support a greater range
- Changed the log messages generated by the celery tasks
- Added the pk of the subscription to the str/repr to aid debugging

1.1.0

- Transition methods that received a `reason` argument now accept a `description` argument,
which is stored on the state log, so that reasons aren't lost. Reason is still valid,
but will not be persisted to the state log. Migrate to using `description`, and it will
log in the state log AND the `reason` field.
`state_unknown`, `renewal_failed`, `end_subscription` are affected.

1.0.1

- SubscriptionState.choices is now sorted, so that the order is consistent between python versions,
and migrations are not generated by applications.

1.0.0

- **Breaking Change** `suspended_timeout` now triggers for subscriptions in SUSPENDED state that are
`timeout_hours` past the `subscription.end` time. It used to trigger if `subscription.last_updated`
hadn't changed for `timeout_hours`, but if `trigger_suspended` was running daily, the subscription
was constantly being updated, and `trigger_suspended_timeout` would never find a record to `end()`.

Page 1 of 2

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.