Technical debt: Monitor Blog Post refactoring work

Context

This is a follow-up to Technical debt: The blog post class is bloated (#20180 - closed). After running through one successful run in a real life scenario, we're going in monitoring mode where we'd like to keep an eye on the behaviour of the blog post generation for the next couple of planned (and unplanned) patch releases.

Exit criteria

• The following patch releases should be go without any major issues or errors

  • August 13th 2025
  • August 27th 2025
  • September 10th 2025
  • Release 17.11.7 (successful pipeline)
  • Release 18.2.4

• Any non-flaky errors OR unexpected behaviours must be addressed and the due date must be pushed back by at least 2 patch releases

  • Add any flaky issues here

Errors

Odd behaviours

• Fix typo in single version template (🧵 see comment thread for context)

What's next?

After completing items above, the following items will be tackled:

• Draft: Remove legacy blog post merge request logic (gitlab-org/release-tools!4079 - closed)
  • Delete the BlogPost::LegacyMergeRequest and related specs
  • Remove references to the feature flag refactored_blog_merge_request_flow
• Delete the feature flag refactored_blog_merge_request_flow
• Draft: Rename blog post metadata template (gitlab-org/release-tools!4080 - closed)