`devops::release` issues without a category label

Attention @ogolowinski and @cstasik, The following issues have been identified in the devops::release stage that do not have a category label. These should be applied with urgency so that important issues are not being lost track of.

  • #13007 PostgreSQL fails to start for Auto Deploy App if Binary Auth is enabled for GCP ~"Release", ~"devops::release", ~"group::progressive delivery"
  • #13004 Enable ci config for autodevops to run on GDK cluster with enabled Binary Authorization ~"Release", ~"devops::release", ~"group::progressive delivery"
  • #13001 (closed) Merge Train does not support squash and merge ~"Accepting merge requests", ~"Release", customer, ~"devops::release", ~"devops::release::merge trains", feature, ~"group::progressive delivery"
  • #12997 (closed) Merge Train text helper is misleading for Merge Immediately case ~"Release", UX debt, ~"devops::release", ~"devops::release::merge trains", ~"group::progressive delivery"
  • #12996 (closed) Cancel redundant pipelines in merge train when reconstruction happens ~"P2", ~"Release", ~"S2", ~"devops::release", ~"devops::release::merge trains", feature, ~"group::progressive delivery"
  • #12971 (closed) Reconstruct Merge Train immediately when master is advanced ~"Release", ~"devops::release", ~"devops::release::merge trains", feature, ~"group::progressive delivery"
  • #11649 (closed) (confidential) ~"(confidential)"
  • #9386 (closed) Avoid overwriting active of feature flag and explicitly define actual_active ~"Release", Stretch, ~"devops::release", ~"technical debt"
  • #9159 Investigate the need of 'Partially Active' state for a Feature Flag ~"Release", ~"devops::release"
  • #9130 (closed) Do not force the creation of per-project ServiceAccount and Namespace ~"Release", ~"devops::release"