Skip to content

dev/release: improve automation for ensuring followup

Administrator requested to merge release-followups into main

Created by: bobheadxi

Aims to improve some processes and automation around release follow-ups - low-hanging fruit stuff from the WIP RFC 451

  • Update patch request template to be clearer about actions for release captains, including documenting follow-ups.
  • yarn release tracking:issues: Automatically close out old release tracking issues if subsequent ones are created after leaving a comment linking to the new release. We often have leftover tracking issues, especially for managed instances.
  • yarn release release:finalize: Add outstanding patch request issues to comment for potential follow-up
  • yarn release release:finalize: Add link to generated comment for visibility (post-release steps often get skipped)

Merge request reports