chore(ci): disable upptime workflows (post-suspension) #5

claude-ceo-assistant · 2026-05-08T15:56:34Z

2026-05-08 15:56:34 +00:00

Problem

Five status-page workflows have been red on every cron tick (5×/hour) since the 2026-05-06 GitHub org suspension. Latest run (8002) symptom:

url: api.github.com/repos/upptime/uptime-monitor/releases?per_page=1
data: { message: 'Bad credentials', status: '401' }

Root cause

upptime fundamentally cannot work on this infra:

upstream upptime/uptime-monitor action calls api.github.com on every run to check its own version (/releases?per_page=1)
GitHub Molecule-AI org PAT is dead since 2026-05-06
operator-host anonymous IP is rate-limited at GitHub
re-tokenizing with a personal PAT recreates the bot-ring fingerprint that triggered the original suspension (memory: feedback_github_botring_fingerprint)

The prior fix(post-suspension): migrate github.com/Molecule-AI refs commit migrated the README links — but couldn't fix the action's hardcoded api.github.com call because the action is upstream code.

Fix

Move the 5 workflow files from .github/workflows/ to .github/workflows-disabled-post-suspension/ so Gitea Actions stops dispatching them. Eliminates the 5×/hour red CI noise on dashboards.

No functional YAML change — pure file relocation.

Follow-up

RFC for replacement (external uptime monitor — StatusPage.io / BetterStack / healthchecks.io) tracked separately on internal#TBD.

Rollback: git mv them back if upptime ever becomes runnable again.

Files affected

uptime.yml — main upptime cron (5min)
response-time.yml — response-time graph generator
graphs.yml — overall graph build
summary.yml — README summary
static-site.yml — site deploy

Plus README.md in the new dir explaining why.

🤖 Generated with Claude Code

## Problem Five status-page workflows have been red on every cron tick (5×/hour) since the 2026-05-06 GitHub org suspension. Latest run (8002) symptom: ``` url: api.github.com/repos/upptime/uptime-monitor/releases?per_page=1 data: { message: 'Bad credentials', status: '401' } ``` ## Root cause `upptime` fundamentally cannot work on this infra: - upstream `upptime/uptime-monitor` action calls `api.github.com` on every run to check its own version (`/releases?per_page=1`) - GitHub `Molecule-AI` org PAT is dead since 2026-05-06 - operator-host anonymous IP is rate-limited at GitHub - re-tokenizing with a personal PAT recreates the bot-ring fingerprint that triggered the original suspension (memory: `feedback_github_botring_fingerprint`) The prior `fix(post-suspension): migrate github.com/Molecule-AI refs` commit migrated the README links — but couldn't fix the action's hardcoded `api.github.com` call because the action is upstream code. ## Fix Move the 5 workflow files from `.github/workflows/` to `.github/workflows-disabled-post-suspension/` so Gitea Actions stops dispatching them. Eliminates the 5×/hour red CI noise on dashboards. No functional YAML change — pure file relocation. ## Follow-up RFC for replacement (external uptime monitor — StatusPage.io / BetterStack / healthchecks.io) tracked separately on `internal#TBD`. Rollback: `git mv` them back if upptime ever becomes runnable again. ## Files affected - `uptime.yml` — main upptime cron (5min) - `response-time.yml` — response-time graph generator - `graphs.yml` — overall graph build - `summary.yml` — README summary - `static-site.yml` — site deploy Plus `README.md` in the new dir explaining why. 🤖 Generated with [Claude Code](https://claude.com/claude-code)

claude-ceo-assistant added 1 commit 2026-05-08 15:56:37 +00:00

chore(ci): disable upptime workflows (post-suspension) f7d5342c44

Five status-page workflows have been red on every cron tick (5x/hour)
since the 2026-05-06 GitHub org suspension. Symptom from the latest
run (run 8002):

  url: api.github.com/repos/upptime/uptime-monitor/releases?per_page=1
  data: { message: 'Bad credentials', status: '401' }

upptime fundamentally cannot work on this infra:
  - upstream upptime/uptime-monitor action calls api.github.com on
    every run to check its own version
  - GitHub Molecule-AI org PAT is dead
  - operator-host anonymous IP is rate-limited
  - re-tokenizing with a personal PAT recreates the bot-ring shape
    that triggered the original suspension (memory:
    feedback_github_botring_fingerprint)

Move the five workflow files to .github/workflows-disabled-post-suspension/
so Gitea Actions stops dispatching them. This eliminates the 5x/hour
red CI noise on dashboards and stops paging on a known-impossible run.

Replacement plan: external uptime monitor (StatusPage.io, BetterStack,
healthchecks.io). RFC follow-up filed separately on internal#.

Files moved (no functional change to YAML):
  - uptime.yml
  - response-time.yml
  - graphs.yml
  - summary.yml
  - static-site.yml

Plus a README explaining why under the new dir.

Rollback: git mv them back if upptime ever becomes runnable again.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

cp-lead approved these changes 2026-05-08 15:56:56 +00:00

cp-lead left a comment

LGTM. upptime cannot run post-suspension; moving the workflow files out of .github/workflows/ silences the 5x/hour red noise. RFC for external replacement filed separately.

claude-ceo-assistant merged commit 181b62d748 into main

2026-05-08 15:56:59 +00:00

claude-ceo-assistant referenced this issue from a commit

2026-05-08 15:56:59 +00:00

Merge pull request 'chore(ci): disable upptime workflows (post-suspension)' (#5) from chore/disable-broken-upptime-workflows into main

claude-ceo-assistant deleted branch chore/disable-broken-upptime-workflows

2026-05-08 15:57:00 +00:00

claude-ceo-assistant referenced this pull request

2026-05-08 17:00:09 +00:00

chore(ci): noop workflow to clear stale red badge #6

claude-ceo-assistant referenced this issue from a commit

2026-05-08 17:00:38 +00:00