fix(ci): avoid protected main push in uptime probe #28

2026-05-22T18:11:01Z

hongming commented

2026-05-22 18:11:01 +00:00

Fixes the remaining post-merge uptime probe failure after #27.

Root cause:
The probe itself succeeded, but the final git push origin HEAD:main was rejected by Gitea pre-receive on protected main with an internal server error. The previous HB env fix is included here too because this branch is from main.

Change:

Export HB for the Python heartbeat writer.
Push generated probe history to uptime-probe-results instead of protected main.

Validation:

comprehensive-testing: parsed .gitea/workflows/uptime-probe.yml with Ruby YAML.load_file; ran git diff --check; confirmed latest probe reached all endpoints successfully and failed only on protected main push.
local-postgres-e2e: not applicable; workflow-only status repo change.
staging-smoke: uptime probe is the smoke surface; latest run showed all seven endpoint probes success=true before push failure.
root-cause: protected-branch push rejection after successful probe/aggregate.
five-axis-review: correctness, security, operability, compatibility, rollback reviewed; no credentials added.
no-backwards-compat: no legacy compatibility needed; branch target change avoids direct protected main mutation.
memory-consulted: followed prior Gitea CI/status monitoring guidance.

Fixes the remaining post-merge uptime probe failure after #27. Root cause: The probe itself succeeded, but the final `git push origin HEAD:main` was rejected by Gitea pre-receive on protected `main` with an internal server error. The previous `HB` env fix is included here too because this branch is from `main`. Change: - Export `HB` for the Python heartbeat writer. - Push generated probe history to `uptime-probe-results` instead of protected `main`. Validation: - [x] comprehensive-testing: parsed `.gitea/workflows/uptime-probe.yml` with Ruby `YAML.load_file`; ran `git diff --check`; confirmed latest probe reached all endpoints successfully and failed only on protected main push. - [x] local-postgres-e2e: not applicable; workflow-only status repo change. - [x] staging-smoke: uptime probe is the smoke surface; latest run showed all seven endpoint probes success=true before push failure. - [x] root-cause: protected-branch push rejection after successful probe/aggregate. - [x] five-axis-review: correctness, security, operability, compatibility, rollback reviewed; no credentials added. - [x] no-backwards-compat: no legacy compatibility needed; branch target change avoids direct protected main mutation. - [x] memory-consulted: followed prior Gitea CI/status monitoring guidance.

hongming added 1 commit 2026-05-22 18:11:01 +00:00

fix(ci): avoid protected main push in uptime probe

CI / all-required (pull_request) Successful in 2s

Details

CI / noop (pull_request) Successful in 1s

Details

CI / Workflow YAML lint (pull_request) Successful in 3s

Details

sop-checklist-gate / gate (pull_request) Successful in 2s

Details

sop-checklist / all-items-acked (pull_request) acked: 7/7 — body-unfilled: 7

Details

4b7cabe378

core-devops commented

2026-05-22 18:11:21 +00:00

/sop-ack comprehensive-testing
/sop-ack local-postgres-e2e
/sop-ack staging-smoke
/sop-ack five-axis-review
/sop-ack memory-consulted

/sop-ack comprehensive-testing /sop-ack local-postgres-e2e /sop-ack staging-smoke /sop-ack five-axis-review /sop-ack memory-consulted

release-manager commented

2026-05-22 18:11:22 +00:00

/sop-ack root-cause
/sop-ack no-backwards-compat

/sop-ack root-cause /sop-ack no-backwards-compat

core-devops approved these changes 2026-05-22 18:13:43 +00:00

core-devops left a comment

Approved uptime probe protected-main push fix after green CI.

infra-sre approved these changes 2026-05-22 18:13:44 +00:00

infra-sre left a comment

Approved uptime probe protected-main push fix after green CI.

hongming merged commit 7ba47cee38 into main

2026-05-22 18:13:44 +00:00

hongming referenced this issue from a commit

2026-05-22 18:13:45 +00:00

Merge pull request #28 from uptime probe protected-main fix

Sign in to join this conversation.

4 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: molecule-ai/molecule-ai-status#28