The spec-prod action computes the "Previous Version" link itself for publication to /TR and passed it to Bikeshed on the command-line with --md-previous-version. Command line argument should override the metadata entry in the spec source. However, with Previous Version, this rather adds an entry to the list.
The net result is that specs that have something like the typical Previous Version: from biblio metadata end up with two "Previous Version" links, instead of one:
https://www.w3.org/TR/2021/WD-webcodecs-20210427/
I've had an idea in my back pocket for the ability to clear a metadata coming from previous levels, but haven't had a good use-case to justify working on it. This sounds reasonable.
The spec-prod action computes the "Previous Version" link itself for publication to /TR and passed it to Bikeshed on the command-line with
--md-previous-version
. Command line argument should override the metadata entry in the spec source. However, withPrevious Version
, this rather adds an entry to the list.The net result is that specs that have something like the typical
Previous Version: from biblio
metadata end up with two "Previous Version" links, instead of one: https://www.w3.org/TR/2021/WD-webcodecs-20210427/Could the override be a real override?
cc @sidvishnoi, @deniak