molecule-core/.gitea/scripts
Molecule AI Core-DevOps 235a8abc12
All checks were successful
Block internal-flavored paths / Block forbidden paths (pull_request) Successful in 19s
Lint curl status-code capture / Scan workflows for curl status-capture pollution (pull_request) Successful in 15s
Secret scan / Scan diff for credential-shaped strings (pull_request) Successful in 18s
CI / Detect changes (pull_request) Successful in 55s
sop-tier-check / tier-check (pull_request) Successful in 20s
E2E API Smoke Test / detect-changes (pull_request) Successful in 55s
E2E Staging Canvas (Playwright) / detect-changes (pull_request) Successful in 59s
Handlers Postgres Integration / detect-changes (pull_request) Successful in 1m3s
Runtime PR-Built Compatibility / detect-changes (pull_request) Successful in 54s
CI / Platform (Go) (pull_request) Successful in 14s
CI / Canvas (Next.js) (pull_request) Successful in 10s
CI / Shellcheck (E2E scripts) (pull_request) Successful in 12s
CI / Python Lint & Test (pull_request) Successful in 14s
E2E API Smoke Test / E2E API Smoke Test (pull_request) Successful in 14s
Handlers Postgres Integration / Handlers Postgres Integration (pull_request) Successful in 10s
E2E Staging Canvas (Playwright) / Canvas tabs E2E (pull_request) Successful in 13s
Runtime PR-Built Compatibility / PR-built wheel + import smoke (pull_request) Successful in 9s
audit-force-merge / audit (pull_request) Successful in 24s
CI / Canvas Deploy Reminder (pull_request) Has been skipped
fix(sop-tier-check): flip jq install to apt-get-first (infra#241 follow-up)
GitHub releases are unreachable from Gitea Actions runners on 5.78.80.188
— curl to github.com times out after ~3s instead of waiting for the
60s timeout. The previous GitHub-first / apt-get-fallback approach
always hit the timeout and never reached apt-get.

Changes:
- `.gitea/workflows/sop-tier-check.yml`: Install jq step now tries
  apt-get first, then GitHub binary as secondary fallback.
  Extended timeout to 120s for the GitHub download in case it
  is reachable on some runner networks.
- `.gitea/scripts/sop-tier-check.sh`: script-level fallback also
  uses apt-get first, then GitHub, then respects SOP_FAIL_OPEN=1
  (set in workflow step) to exit 0 so CI never blocks.

Combined with continue-on-error: true at step level and SOP_FAIL_OPEN=1,
this makes sop-tier-check CI resilient to any jq installation failure.

Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
2026-05-11 08:19:02 +00:00
..
tests fix(sop-tier-check): clause splitter strips newlines, OR-set collapses to one token (#229) 2026-05-09 22:03:12 -07:00
audit-force-merge.sh ci(audit-force-merge): fan §SOP-6 force-merge audit to molecule-core 2026-05-08 20:09:35 -07:00
ci-required-drift.py feat(internal#219 §4+§6): port ci-required-drift + audit-force-merge sidecar from CP 2026-05-11 00:35:25 -07:00
main-red-watchdog.py feat(ci): main-red watchdog (Option C of main-never-red directive) — closes #420 2026-05-11 00:36:20 -07:00
sop-tier-check.sh fix(sop-tier-check): flip jq install to apt-get-first (infra#241 follow-up) 2026-05-11 08:19:02 +00:00