Refs #576: Reject C1 controls in deploy settings#623
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
📝 WalkthroughWalkthroughThis PR refactors control-character validation in deploy settings by extracting a shared helper function and expanding its detection range. The new ChangesControl Character Validation Refactor
🚥 Pre-merge checks | ✅ 6✅ Passed checks (6 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Comment |
Refs #576
Summary
Evidence
Before the fix, a local probe showed internal
\x85values in deploy strings such asMERGEWORK_ADMIN_TOKEN,MERGEWORK_GITHUB_OAUTH_CLIENT_ID, andMERGEWORK_DATABASE_URLdid not produce the existing control-character validation error.Validation
uv run --extra dev python -m pytest tests/test_deploy_readiness.py::test_deploy_readiness_rejects_c1_control_characters -q-> 1 passeduv run --extra dev python -m pytest tests/test_deploy_readiness.py -q-> 28 passeduv run --extra dev python -m pytest -q-> 483 passed, 1 warninguv run --extra dev ruff check app/config.py tests/test_deploy_readiness.py-> passeduv run --extra dev ruff format --check app/config.py tests/test_deploy_readiness.py-> 2 files already formatteduv run --extra dev mypy app/config.py-> successuv run --extra dev python scripts/docs_smoke.py-> docs smoke okgit diff --check-> cleanNo private data, secrets, admin token values, wallet material, production mutation, price/liquidity/exchange/bridge/off-ramp claims, or fabricated payout claims are included.
Summary by CodeRabbit