fix(dotenv): reserve workspace OPENCLAW env namespace#69376
Conversation
Greptile SummaryThis PR reserves the Confidence Score: 5/5Safe to merge — the security fix is correct, well-tested, and intentionally minimal. The core change (adding No files require special attention. Reviews (2): Last reviewed commit: "fix(dotenv): reserve workspace OPENCLAW ..." | Re-trigger Greptile |
|
@greptile review |
|
@codex review |
|
Codex Review: Didn't find any major issues. Another round soon, please! ℹ️ About Codex in GitHubCodex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
If Codex has suggestions, it will comment; otherwise it will react with 👍. When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback". |
3bc7a68 to
3867c31
Compare
3867c31 to
f4a634e
Compare
Summary
OPENCLAW_*namespace for trusted shell and global runtime env input.envruntime-control keys instead of relying on per-key denylist updatesChanges
OPENCLAW_workspace dotenv prefix guard insrc/infra/dotenv.tsValidation
corepack pnpm test src/infra/dotenv.test.ts src/cli/update-cli.test.tstimeout 120s claude -p "/review"and got a ship-it review with only optional cleanup suggestionspnpm check:changed --stagedhit unrelated existing infra failures insrc/infra/restart-stale-pids.test.ts,src/infra/host-env-security.test.ts,src/infra/run-node.test.ts,src/infra/git-commit.test.ts, andsrc/infra/update-check.test.tsNotes
.envpathOPENCLAW_*entries in the denylist are now redundant, but I left that cleanup out to keep the fix minimal