Skip to content

refactor(cloud): remove mitmproxy flags - #102

Merged
riglar merged 1 commit into
devfrom
refactor/remove-mitm-flags
Aug 3, 2026
Merged

refactor(cloud): remove mitmproxy flags#102
riglar merged 1 commit into
devfrom
refactor/remove-mitm-flags

Conversation

@riglar

@riglar riglar commented Aug 3, 2026

Copy link
Copy Markdown
Contributor

Removes the enterprise-only --mitmHost / --mitmPath flags and everything downstream of them.

Changes

  • src/config/flags/environment.flags.ts — both flag definitions.
  • src/commands/cloud.ts — the two arg reads and the --mitmPath requires --mitmHost validation.
  • src/services/test-submission.service.ts — the TestSubmissionConfig fields, their destructuring, and the two configPayload keys.
  • src/mcp/tools/run-cloud-test.ts — drops mitm from the doc comment listing what the MCP tool doesn't do.

No test or doc referenced these flags; no mitm string remains in the repo.

Wire compatibility

The submitted config payload is unchanged for existing runs: both keys were undefined when the flags were unset, and JSON.stringify drops undefined keys — so submissions that never passed the flags produce byte-identical fields.

Back-compat note

Citty doesn't reject unknown flags, so an existing invocation passing --mitmHost=… will now be silently ignored rather than erroring — it keeps running, but stops proxying. If we'd rather it fail loudly, a follow-up can add an explicit "flag removed" error for those two names.

Titled refactor (patch bump) rather than carrying a !: per CLAUDE.md, a breaking marker on 5.x means a real major bump, which seems disproportionate for retiring an enterprise-only flag. Retitle if you want the major.

Verification

  • pnpm typecheck — passes.
  • pnpm lint — 0 errors (32 pre-existing unused-eslint-disable warnings, all in untouched files).

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

Drops the enterprise-only --mitmHost / --mitmPath flags and everything
downstream of them:

- environment.flags.ts: both flag definitions
- cloud.ts: the arg reads and the "--mitmPath requires --mitmHost" check
- test-submission.service.ts: TestSubmissionConfig fields, destructuring,
  and the two configPayload keys
- run-cloud-test.ts: the doc comment listing what the MCP tool omits

The submitted config payload is unchanged for existing runs: both keys
were undefined when the flags were unset, and JSON.stringify drops
undefined, so submissions that never passed them stay byte-identical.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@claude

claude Bot commented Aug 3, 2026

Copy link
Copy Markdown

Code review

No issues found. Checked for bugs and CLAUDE.md compliance.

@riglar
riglar merged commit 3888fc5 into dev Aug 3, 2026
10 checks passed
@riglar
riglar deleted the refactor/remove-mitm-flags branch August 3, 2026 14:00
@finalerock44 finalerock44 mentioned this pull request Aug 6, 2026
14 tasks
finalerock44 added a commit that referenced this pull request Aug 7, 2026
Promote from dev to stable:

* feat: client-side envelope encryption of app binaries, flow zips and env vars
  (#94, #101) — opt-in via `--encrypt` / `DCD_ENCRYPT_BINARIES=1` and off by
  default, so uploads stay byte-identical unless asked for. Per-upload DEK,
  chunked AES-256-GCM container, X25519 sealed-box DEK wrap; encrypted binaries
  dedup on the plaintext hash so re-uploads still hit the cache.
* feat(artifacts): prefer server-assembled bundle delivery for downloads (#93) —
  falls back to the inline endpoint on 501, so it degrades cleanly against an
  API that has not shipped bundles.
* feat(device): add Android API level 37 (Android 17) (#107) — the flag enum
  accepts 37, but the device/API-level pair is validated against the
  compatibility matrix the *target* API serves, and production still tops out at
  36, so 37 is refused client-side until the platform gate flips.
* refactor(cloud): remove the enterprise-only --mitmHost / --mitmPath flags
  (#102). The submitted config payload for runs that never passed them is
  byte-identical.
* fix(deps) / deps: clear every outstanding pnpm audit advisory (#89, #92, #95,
  #100, #106), bump chalk 5 -> 6, and regenerate the schema types from the
  current API swagger (#105).

No platform prerequisite this time: the envelope decrypt half (dcd api +
simulators) is already on production with both env KEK public keys pinned,
bundle delivery has a 501 fallback, and API 37 is gated server-side.

Carries only the source delta — package.json version, CHANGELOG.md and the
release-please manifests stay as release-please left them on production.

Release-As: 5.3.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant