94de4acef50f4bbc997ad44495414c56337ab16d
4
Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
|
|
4c47e151f3 |
chore(ci): add missing timeout-minutes guards to hot-path jobs
CI (SIAX Cloud) / integration (push) Skipped
masterplan-lock / check (push) Successful in 6s
masterplan-lock / check (pull_request) Successful in 6s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 24s
Security Scan (SIAX Cloud) / security (push) Successful in 49s
CI (SIAX Cloud) / security (push) Successful in 53s
CI (SIAX Cloud) / quality (push) Successful in 1m20s
CI (SIAX Cloud) / security (pull_request) Successful in 20s
CI (SIAX Cloud) / quality (pull_request) Successful in 53s
CI (SIAX Cloud) / integration (pull_request) Successful in 1m0s
Fleet-wide CI-speed pass: none of 0pt's push/pull_request-triggered workflow jobs capped their own runtime, so a hang (network stall, runaway process, stuck polling loop) burns a runner slot until Gitea's own default kicks in. Added job-level timeout-minutes sized to what each job actually does: cd.yml deploy 20 (bounded ~10min signed-artifact poll + setup) ci.yml quality 30 (typecheck/test/build) ci.yml integration 45 (multi-service: live OpenSearch + ClickHouse) ci.yml security 15 (single trivy fs scan) security.yml security 15 (single trivy fs scan) masterplan-lock.yml check 10 (single dependency-free shell check) release.yml release 45 (docker build/push + full G17 SBOM/scan/attest/verify chain) Deliberately NOT included in this PR: a concurrency: block for ci.yml/security.yml/masterplan-lock.yml's push+pull_request double- trigger. ci.yml's own `integration` job comment already documents, measured live (runs 28904/28906), that "Gitea currently ignores workflow concurrency" on this fleet, and the repo's real fix for the resulting double-run-on-shared-service-containers problem is the self-identifying-container pattern already in that job, not a concurrency group. Adding an inert concurrency: block here would give false confidence that the duplicate-run problem is handled when it measurably is not. Left for a follow-up decision once that fleet-wide finding is resolved. Part of a fleet-wide CI-speed pass (timeout-minutes audit). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
1322d26fac |
fix(ci): make the required security gate capable of failing
Branch protection on `main` requires exactly two status contexts:
CI (SIAX Cloud) / security (push)
CI (SIAX Cloud) / quality (push)
The `security` half could not fail. All three Trivy invocations in this
repo ran with `--exit-code 0`, so the scanner reported findings to stdout
and then exited 0 regardless.
Measured on main @4514d97, 2026-09-08, same scanner (Trivy 0.73.0), same
target, only the flag differing:
A --exit-code 0, clean tree -> exit 0
B --exit-code 0, planted AWS secret access key -> exit 0 (DETECTED
as CRITICAL in the report, gate still green)
C --exit-code 1, same planted secret -> exit 1
D --exit-code 1, probe removed -> exit 0
B is the defect: the required context reported success while the scanner
had a CRITICAL secret in hand. D is why this is safe to land now -- the
tree is clean today, so flipping the flag does not open the gate red.
(PR #19 measured 19 HIGH findings on 2026-08-11; those dependencies have
since been updated on main, 142 commits later.)
The other required context, `quality`, was verified real and left alone:
a planted type error fails `pnpm run typecheck` (exit 2) and a planted
failing assertion fails `pnpm run test` (exit 1, 945 passed baseline).
nightly.yml carried the same flag. A nightly scan exists to catch CVEs
published against code that did not change; with `--exit-code 0` it could
never raise that alarm.
Not fixed here, needs an owner decision: services/scrapers/requirements.txt
uses `>=` ranges only. Trivy's pip scanner cannot resolve unpinned
specifiers, so it omits the file from the scan entirely -- it never appears
as a target. Pinning those same floors with `==` surfaces 3 HIGH findings
(aiohttp CVE-2025-69223, aiohttp CVE-2026-69244, lxml CVE-2026-41066).
Deliberately NOT suppressed with `--skip-dirs`, which would turn a
measurable blind spot into declared policy.
Job names are unchanged, so both required context strings are preserved.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
|
||
|
|
2393f52768 |
docs(compliance): finish attributing the evasion-stack keep decision
CI (SIAX Cloud) / security (push) Successful in 20s
Security Scan (SIAX Cloud) / security (push) Successful in 20s
CI (SIAX Cloud) / quality (push) Successful in 41s
CI (SIAX Cloud) / security (pull_request) Successful in 20s
Security Scan (SIAX Cloud) / security (pull_request) Successful in 20s
CI (SIAX Cloud) / quality (pull_request) Successful in 41s
PR #15 already fixed AGENTS.md/SECURITY.md with a dated, attributed statement of the account owner's 2026-08-11 decision (Simon Axelsson, via an interactive decision prompt, responding to this repo's own removal proposal PR #7 which was verified clean/128 tests and closed unmerged -- no rationale beyond "keep it" was given or is invented). This PR finds and fixes every other place in the repo that still carried the earlier unattributed "medvetet anvandarbeslut" / "deliberate user decision" claim a compliance audit flagged as unverifiable: - docs/compliance/GOLDEN-STANDARD-REPORT.md: control C6 row + the "Bypass-undantag" formal section (the two places this doc was explicitly named to need checking) -- header gains a dated update note, C6 row and the section body get the same attributed statement as AGENTS.md/SECURITY.md. - docs/compliance/SLUTRAPPORT.md, docs/compliance/INVENTORY.md: historical session doc keeps its original text and gains a dated correction addendum; the INVENTORY.md evidence bullet is corrected in place. - docs/slo.md, CONTRIBUTING.md, prompts/002-compliance-audit.md, renovate.json, .gitea/workflows/security.yml: direct/living references to the exemption get the same attributed, dated pointer instead of the unattributed phrase. CLAUDE.md's general §1 anti-evasion policy text is untouched, per instruction -- this is a scoped exception note, not a change to the normative rule. No code changes. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> |
||
|
|
48d31d0081 | ci(workflows): split CD/security/nightly under .gitea/workflows + gitignore hygiene (protected-path PR) |