Consider removing the list of post-deploy migrations included in each package
As part of &585 (closed), a message is posted on the release issue every time a package includes post-migrations, example gitlab-org/release/tasks#3752 (comment 931075058). The purpose of this message was to have a log of auto-deploy packages that included post-migrations in case we were required to rollback.
During #2356 (closed), we discovered that information wasn't enough: it helped us to know which packages introduced post-migrations but it didn't help us to know if we could rollback to a specific package. As a consequence, the rollback approach changed: instead of relying on the auto-deploy packages we'll establish a point of no return in time that allow us to rollback to any package up until that point (see #2356 (comment 920162305) for more info); as an aside, the execution of the post-deploy pipeline is going to post a message on the release issue with the list of the post-migrations to be executed #2362 (closed)
This makes the original message no longer useful:
- While informative, it's not clear what actions could be performed based on that information.
- The release issue acts like an audit issue, tracking the deployment actions performed. The post-migration message is not associated to any action, it is supposed to be an informative one.
Lets utilize this issue to discuss if we should keep the post-deploy migration message.