Safe Linking

[trieloff]

See https://cq-dev.slack.com/archives/CGG9B79BK/p1609701306002100?thread_ts=1609615520.001500&cid=CGG9B79BK

If the v1 link is not pointing to the latest version it is likely that a rollback has been performed. It's probably better not to update links in that case and instead wait for the operator to re-link using action-admin.

[trieloff]

good idea with the safe linking. but this way we cannot easily deploy a fix w/o a special flag ...

There are a number of practical considerations that I didn't want to think through last night:

• how to indicate you have a fix for that specific rollback
• how to determine that the linked version is not the last one (without excessive reads)

One possible solution:

1. When rolling back using the action admin, automatically create a github issue and add the issue URL to the v1 metadata.
2. As an operator, use the github issue to describe reasoning for the rollback
3. When attempting to link, check that the github issue has been resolved

The only additional overhead would be to add the fixes #53 line to the commit fixing the issue.