OpenAI's Codex Security CLI and TypeScript SDK for finding, validating, and fixing security vulnerabilities. npm: https://www.npmjs.com/package/@openai/codex-security
TypeScript ai-securityapplication-securityclicode-scanningcodexcodex-securitycybersecuritydevsecopsnodejsnpmopenaisdksecuritytypescriptvulnerability-scanning
docs(ci): explain how to avoid duplicate native builds when landing PRs (#1955)
Michael D'Angelo19393c6010a3
diff --git a/docs/ci.md b/docs/ci.mdindex ba5b37b66..27199d187 100644--- a/docs/ci.md+++ b/docs/ci.md@@ -106,3 +106,15 @@ When measuring CI changes, separate time to required-green from summed jobexecution time, prerequisite waits, runner scheduling, approval waits, andmanual retry delays. Compare matching revisions and test configurations, andrecord failures as well as successful runs.++When a batch of merges can wait, check **Restore verified native payload** in+an active `node-ci` push or scheduled run on `main`. On a miss, another push+with the same inputs can start all eight platform builds again. Before merging+a PR that leaves those inputs unchanged, look for the exact key in+`gh cache list --ref refs/heads/main --key KEY`. Once it is there, it does not+matter which `main` run saved it. Different inputs can build in parallel.++The key uses the UTC week and the paths listed in **Identify native build and+proof inputs**. Compare the next change against current `main`: its PR run may+have tested an older base or skipped native preparation entirely. PR runs+cannot populate this cache for `main`.