Releases: javrasya/django-river
Releases · javrasya/django-river
3.3.0
3.2.2
3.2.1
3.2.0
3.1.4
3.1.3
3.1.2
3.1.1
3.1.0
3.0.0
🎉 🎉 🎉 🎉 🎉 🎉 🎉 🎉
We are very happy to announce that we are releasing django-river
v3.0.0 with too many improvements and critical bug fixes. We are also working on a shiny user interface for django-river
administration which will be published soon.
Stay tuned :-)
- 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.