From 1a8e601a1786ab39ed4c1b2daf156998779072fe Mon Sep 17 00:00:00 2001 From: Pigbibi <20649888+Pigbibi@users.noreply.github.com> Date: Sun, 30 Aug 2026 10:32:34 +0800 Subject: [PATCH] fix: publish lifecycle status after monitor alerts Co-Authored-By: Codex --- .github/workflows/runtime-target-lifecycle.yml | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.github/workflows/runtime-target-lifecycle.yml b/.github/workflows/runtime-target-lifecycle.yml index f2832e3..13dcacf 100644 --- a/.github/workflows/runtime-target-lifecycle.yml +++ b/.github/workflows/runtime-target-lifecycle.yml @@ -95,8 +95,10 @@ jobs: RUNTIME_GUARD_FAIL_WORKFLOW_ON_ALERT: "true" run: | set -uo pipefail + set +e python scripts/cloud_run_runtime_guard.py > runtime-guard.log 2>&1 exit_code=$? + set -e cat runtime-guard.log if [ "$exit_code" -eq 0 ]; then status=pass @@ -128,8 +130,10 @@ jobs: exit 0 fi + set +e python scripts/execution_report_heartbeat.py > execution-heartbeat.log 2>&1 exit_code=$? + set -e cat execution-heartbeat.log if [ "$exit_code" -eq 0 ] && grep -qi 'heartbeat skipped' execution-heartbeat.log; then status=not_due