Currently we have a pattern where we deal with getting the default revision and optionally the most recent forward revision (draft revision that is ahead of default). But in reality it is more safe to operate on all forward reviisions because we never know which one a person might publish in their workflow. A common editorial pattern is to have a number of staged forward revisions and then publish intermediary ones at certain times. We want to support that by making changes to ALL forward revisions.
Active
1.0
Code
I think the example added by ✨ Add script example for node operation. Active is going to use this pattern. So All that would remain for this ticket would be to add an FAQ to the readme that points to the section of the code in the example script.