Missing workflow step re updating `.smpte-build.json`?

[thomasheritage]

https://doc.smpte-doc.org/html-pub/main/#sec-document-github-releases states:

The latestEditionTag property in the .smpte-build.json file shall always be equal to the name of the most recent git tag.

And @SteveLLamb just updated .smpte-build.json on the main branch in the ST 2067-206 repo to set the latestEditionTag property to "20260202-wd". See https://github.com/SMPTE/st2067-206-private/commit/b0b21d6ffb32208f21370e964e7af92fb974bc49

It was still set to null because the document is still at workflow step "7" at https://doc.smpte-doc.org/html-pub/main/#sec-sample-workflow "Comments received on pre-FCD ballot review". .smpte-build.json has been updated on the 20260202-cd1 branch per workflow step "6.c".

Is there a missing workflow step to update .smpte-build.json on main prior to the merge of the 20260202-cd1 branch (which will happen at workflow step "8.b")?

[SteveLLamb]

As yes, that can be more clear that (currently) it needs to be updated manually to the ...the most recent **release's** git tag..

Looking to automating that process to eliminate that requirement in parallel.