From 669a90f726ba0c2619eeb87b005443e1663b663d Mon Sep 17 00:00:00 2001 From: mrbobbytables Date: Thu, 24 Sep 2026 13:07:59 +0000 Subject: [PATCH] docs(launch): fix stale refresh-metrics.yml row in readiness gate Replace the LAUNCH.md launch-readiness gate row that tracked a refresh-metrics.yml workflow which was proposed (PR #125) and declined (#74) with a row pointing at the collect:metrics + validate:metrics steps that actually run inside import-architectures.yml, sharing that workflow's tracking issue (#121) and readiness signal. Hive-Run: cncf/endusers#557 Hive-Plan: docs-launch-md-refresh-metrics-row-fix Hive-Spec: LAUNCH.md#launch-readiness-gate-zero-red-content-pipelines Signed-off-by: mrbobbytables --- LAUNCH.md | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-) diff --git a/LAUNCH.md b/LAUNCH.md index 5f8fdb96..099a3921 100644 --- a/LAUNCH.md +++ b/LAUNCH.md @@ -74,11 +74,15 @@ shipping stale content on day one — the exact failure this automation exists t prevent. Before the W-0 launch date, all scheduled content-refresh workflows must be green for **2 consecutive scheduled runs**: -| Pipeline | Schedule | Tracking | -| ----------------------------------------------------------- | -------- | ------------ | -| Import reference architectures (`import-architectures.yml`) | daily | #121 | -| Refresh community profiles (`refresh-community-people.yml`) | weekly | #122 | -| Metrics refresh (`refresh-metrics.yml`, not yet merged) | daily | #74, PR #125 | +| Pipeline | Schedule | Tracking | +| -------------------------------------------------------------------------------------------- | -------- | -------- | +| Import reference architectures (`import-architectures.yml`) | daily | #121 | +| Refresh community profiles (`refresh-community-people.yml`) | weekly | #122 | +| Metrics refresh (`collect:metrics` + `validate:metrics` steps of `import-architectures.yml`) | daily | #121 | + +A dedicated `refresh-metrics.yml` workflow was proposed in PR #125 and declined +(#74); metrics refresh instead runs as steps inside `import-architectures.yml`, +so it shares that workflow's tracking issue and readiness signal. If any pipeline is still red at W-1, treat it the same as any other Phase 1 blocker under "Full content freeze rehearsal" (W-4): either land the fix or