sus-vector-fix-new-v3.1.1 #690
13
CHANGELOG.md
13
CHANGELOG.md
@ -16,12 +16,21 @@ will consitute of a breaking change warranting a new major release:
|
|||||||
|
|
||||||
# [unreleased]
|
# [unreleased]
|
||||||
|
|
||||||
|
# [v2.0.5] to be released
|
||||||
|
|
||||||
|
- The dual lane assembly transition failed handler started new transitions towards the current mode
|
||||||
|
instead of the target mode. This means that if the dual lane assembly never reached the initial
|
||||||
|
submode (e.g. mode normal and submode dual side), it will transition back to the current mode,
|
||||||
|
which miht be `MODE_OFF`. Furthermore, this can lead to invalid internal states, so the subsequent
|
||||||
|
recovery handling becomes stuck in the custom recovery sequence when swichting power back on.
|
||||||
|
- The dual lane custom recovery handling was adapted to always perform proper power switch handling
|
||||||
|
irrespective of current or target modes.
|
||||||
|
|
||||||
# [v2.0.4] 2023-04-19
|
# [v2.0.4] 2023-04-19
|
||||||
|
|
||||||
## Fixed
|
## Fixed
|
||||||
|
|
||||||
- The dual lane assembly device handlers did not properly set their datasets
|
- The dual lane assembly datasets were not marked invalid properly on OFF transitions.
|
||||||
to invalid on off transitions
|
|
||||||
|
|
||||||
# [v2.0.3] 2023-04-17
|
# [v2.0.3] 2023-04-17
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user