Django-river

Latest version: v3.3.0

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

Scan your dependencies

Page 2 of 5

3.1.1

-----
* **Bug** - 128_: Available approvals are not found properly when primary key is string
* **Bug** - 129_: Models with string typed primary keys violates integer field in the hooks


.. _128: https://github.com/javrasya/django-river/issues/128
.. _129: https://github.com/javrasya/django-river/issues/129

3.1.0

-----
* **Imrovement** - 123_: Jump to a specific future state of a workflow object
* **Bug** - 124_: Include some BDD tests for the users to understand the usages easier.


.. _123: https://github.com/javrasya/django-river/issues/123
.. _124: https://github.com/javrasya/django-river/issues/124

3.0.0

-----
* **Bug** - 106_: It crashes when saving a workflow object when there is no workflow definition for a state field
* **Bug** - 107_: next_approvals api of the instance is broken
* **Bug** - 112_: Next approval after it cycles doesn't break the workflow anymore. Multiple cycles are working just fine.
* **Improvement** - 108_: Status column of transition approvals are now kept as string in the DB instead of number to maintain readability and avoid mistakenly changed ordinals.
* **Improvement** - 109_: Cancel all other peer approvals that are with different branching state.
* **Improvement** - 110_: Introduce an iteration to keep track of the order of the transitions even the cycling ones. This comes with a migration that will assess the iteration of all of your existing approvals so far. According to the tests, 250 workflow objects that have 5 approvals each will take ~1 minutes with the slowest django `v1.11`.
* **Improvement** - 111_: Cancel all approvals that are not part of the possible future instead of only impossible the peers when something approved and re-create the whole rest of the pipeline when it cycles
* **Improvement** - 105_: More dynamic and better way for hooks.On the fly function and hook creations, update or delete are also supported now. It also comes with useful admin interfaces for hooks and functions. This is a huge improvement for callback lovers :-)
* **Improvement** - 113_: Support defining an approval hook with a specific approval.
* **Improvement** - 114_: Support defining a transition hook with a specific iteration.
* **Drop** - 115_: Drop skipping and disabling approvals to cut the unnecessary complexity.
* **Improvement** - 116_: Allow creating transitions without any approvals. A new TransitionMeta and Transition models are introduced to keep transition information even though there is no transition approval yet.


.. _105: https://github.com/javrasya/django-river/issues/105
.. _106: https://github.com/javrasya/django-river/issues/106
.. _107: https://github.com/javrasya/django-river/issues/107
.. _108: https://github.com/javrasya/django-river/issues/108
.. _109: https://github.com/javrasya/django-river/issues/109
.. _110: https://github.com/javrasya/django-river/issues/110
.. _111: https://github.com/javrasya/django-river/issues/110
.. _112: https://github.com/javrasya/django-river/issues/112
.. _113: https://github.com/javrasya/django-river/issues/113
.. _114: https://github.com/javrasya/django-river/issues/114
.. _115: https://github.com/javrasya/django-river/issues/115
.. _116: https://github.com/javrasya/django-river/issues/116

2.0.0

-----
* **Improvement** - [ 90_, 36_ ]: Finding available approvals has been speeded up ~x400 times at scale
* **Improvement** - 92_ : It is mandatory to provide initial state by the system user to avoid confusion and possible mistakes
* **Improvement** - 93_ : Tests are revisited, separated, simplified and easy to maintain right now
* **Improvement** - 94_ : Support class level hooking. Meaning that, a hook can be registered for all the objects through the class api
* **Bug** - 91_ : Callbacks get removed when the related workflow object is deleted
* **Improvement** - Whole ``django-river`` source code is revisited and simplified
* **Improvement** - Support ``Django v2.2``
* **Deprecation** - ``Django v1.7``, ``v1.8``, ``v1.9`` and ``v1.10`` supports have been dropped

.. _36: https://github.com/javrasya/django-river/issues/36
.. _90: https://github.com/javrasya/django-river/issues/90
.. _91: https://github.com/javrasya/django-river/issues/91
.. _92: https://github.com/javrasya/django-river/issues/92
.. _93: https://github.com/javrasya/django-river/issues/93
.. _94: https://github.com/javrasya/django-river/issues/94

1.0.2

-----
* **Bug** - 77_ : Migrations for the models that have state field is no longer kept getting recreated.
* **Bug** - It is crashing when there is no workflow in the workspace.

.. _77: https://github.com/javrasya/django-river/issues/77

1.0.1

-----
* **Bug** - 74_ : Fields that have no transition approval meta are now logged correctly.
* **Bug** - ``django`` version is now fixed to 2.1 for coverage in the build to make the build pass

.. _74: https://github.com/javrasya/django-river/issues/74

Page 2 of 5

© 2024 Safety CLI Cybersecurity Inc. All Rights Reserved.