fix(ci): add continue-on-error to publish-runtime-autobump (closes #504) #524
Merged
core-lead
merged 1 commits from 2026-05-11 17:46:04 +00:00
sre/scope-operational-workflows-to-schedule into main
1 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
| 6f90193382 |
fix(ci): add continue-on-error to publish-runtime-autobump (closes #504)
All checks were successful
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 18s
CI / Detect changes (pull_request) Successful in 57s
E2E API Smoke Test / detect-changes (pull_request) Successful in 1m2s
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 54s
Lint curl status-code capture / Scan workflows for curl status-capture pollution (pull_request) Successful in 23s
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 16s
sop-tier-check / tier-check (pull_request) Successful in 17s
Handlers Postgres Integration / detect-changes (pull_request) Successful in 50s
Runtime PR-Built Compatibility / detect-changes (pull_request) Successful in 41s
CI / Platform (Go) (pull_request) Successful in 9s
CI / Shellcheck (E2E scripts) (pull_request) Successful in 7s
CI / Python Lint & Test (pull_request) Successful in 8s
CI / Canvas (Next.js) (pull_request) Successful in 9s
CI / Canvas Deploy Reminder (pull_request) Has been skipped
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 9s
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 11s
Runtime PR-Built Compatibility / PR-built wheel + import smoke (pull_request) Successful in 8s
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 8s
audit-force-merge / audit (pull_request) Successful in 12s
publish-runtime-autobump fires on every push to main/staging that touches workspace/. It posts a commit status — and exits non-zero when there's nothing to bump, a DISPATCH_TOKEN is missing, or a tag already exists. None of those mean "the pushed code is broken," but they flip main's combined status to failure and trip the main-red-watchdog, generating false-positive issues (#494, #504). Fix: add `continue-on-error: true` to the autobump-and-tag job so operational failures (infra degradation, missing secrets, pre-existing tags) post success instead of failure. The fail-loud path remains in publish-runtime.yml which tests whether the runtime package actually builds and uploads. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com> |
