Closed peetucket closed 5 years ago
Why is this on 7-2-stable and not on master? I'd expect a change in master first and then a backport to 7-x (probably 7.3) if necessary
fair enough, same change on master: https://github.com/sul-dlss/dor-services/pull/648
...even if it is not the last timestamp
This gets around the issue where we show a status to users in Argo that is incorrect if an earlier workflow step with an earlier lifecycle is manually repeated or triggered during an object remediation. The idea is that if an object has a current lifecycle of accessioned (current being the latest version), it should be considered accessioned regardless of timestamps.