[Automated] Update pip CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to pip CLI options classes.

The generator scraped the latest CLI help output from the installed tool.

Changes

• Updated options classes to reflect latest CLI documentation
• Added new commands if any were detected
• Updated option types and descriptions

Command coverage

Command coverage report:

• pip (pip 24.0 from /usr/lib/python3/dist-packages/pip (python 3.12)): 14 commands, tree a9b92993f96a5cee7b1131d5da44c679e8bd64ee6a736a1d92dc95e915bd18ac
  • Baseline comparison: 14 commands at pip 24.0 from /usr/lib/python3/dist-packages/pip (python 3.12) -> 14 commands at pip 24.0 from /usr/lib/python3/dist-packages/pip (python 3.12)

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[coderabbitai]

Important

Review skipped

Review was skipped due to path filters

⛔ Files ignored due to path filters (17)

• src/ModularPipelines.Python/Generated/Pip.Generation.json is excluded by !**/generated/**
• src/ModularPipelines.Python/Options/PipCacheOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipCheckOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipConfigOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipDownloadOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipFreezeOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipHashOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipIndexOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipInspectOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipInstallOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipListOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipSearchOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipShowOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipUninstallOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Options/PipWheelOptions.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Services/IPip.Generated.cs is excluded by !**/*.generated.*
• src/ModularPipelines.Python/Services/Pip.Generated.cs is excluded by !**/*.generated.*

CodeRabbit blocks several paths by default. You can override this behavior by explicitly including those paths in the path filters. For example, including **/dist/** will override the default block on the dist directory, by removing the pattern from both the lists.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: e2da4e88-0233-4858-8547-803213d4d184

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-15T17:35:00.227351Z	73126bd	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[github-actions]

Code Review: pip CLI options regeneration (#5144)

This is an autogenerated update to the pip Options classes (src/ModularPipelines.Python/Options/Pip*.Generated.cs), driven by tools/ModularPipelines.OptionsGenerator/. Per repo convention, these files should never be hand-edited — findings below point at the generator logic that produced them, not the generated files themselves.

1. Required-collection validation doesn't catch blank/empty elements (correctness)

In PipInstallOptions.Generated.cs (and the equivalent generated Validate() blocks in PipDownloadOptions.Generated.cs / PipWheelOptions.Generated.cs), the new "at least one of X/Y/Z must be specified" check special-cases a few element shapes:

• IEnumerable<char> (i.e. the value is really a single string) → correctly guarded with !string.IsNullOrWhiteSpace(...).
• IEnumerable<KeyValue> / IEnumerable<CliValuePair> → Any(item => item is not null).
• Plain IEnumerable<string> (the common case, e.g. an array literal) → falls through to value is not null && Any(Cast<object>(...), item => item is not null).

That last branch only rejects null, not blank/whitespace-only strings. So new PipInstallOptions { RequirementSpecifier = new[] { "" } } passes validation even though it would produce an effectively-empty CLI argument — the exact case the single-string branch was written to prevent. The generator's element-shape dispatch should apply the same "non-null and non-blank" predicate uniformly for string-typed collections, not just for the single-string special case. Worth fixing in the generator's validation-expression builder rather than patching each generated file (which would just get overwritten on the next run anyway).

2. Per-property duplicate snapshot wrapper classes (design/maintainability)

Each collection-typed property (Requirement, RequirementSpecifier, etc.) gets its own private nested __<Property>SnapshotKeyValue / __<Property>SnapshotCliValuePair class emitted inline, and the body of these classes is identical modulo the captured type parameter (see PipDownloadOptions.Generated.cs:40-74 for two nearly-identical copies in one file, repeated again with different names in PipInstallOptions, PipUninstallOptions, PipWheelOptions, etc.).

This is boilerplate the generator is emitting per call site instead of once. A more maintainable approach would be a single shared generic type in ModularPipelines.Models (e.g. CollectionSnapshot<TSource, TElement> implementing both IEnumerable<TSource> and IEnumerable<TElement>), with the generator emitting only a new CollectionSnapshot<string, KeyValue>(values, keyValues) call at each property. That would cut the generated surface area significantly and mean a future fix to the snapshot behavior only needs to land in one hand-written class instead of being re-emitted correctly by the generator N times per tool.

3. Dead IEnumerable<char> branch on IEnumerable<string>-typed properties (minor, but repeated everywhere)

The setter/validator ternaries test (object)values is IEnumerable<char> even for properties statically typed IEnumerable<string> (e.g. PipDownloadOptions.Generated.cs:37, PipInstallOptions.Generated.cs:401). A value can't simultaneously be assignable to IEnumerable<string> and be IEnumerable<char> in this codebase — that branch appears to be a leftover from a shared per-element-type template that doesn't check whether the "single string" special case is actually reachable for the given T. It's unreachable, but because it's regenerated into every collection property across every options file, it adds up to a fair amount of permanent unreachable complexity that could mislead a future reader debugging validation behavior (e.g., the finding above). Worth having the generator skip emitting that branch when the collection element type isn't itself string-like.

Other notes

• Command coverage in the PR description shows no command/count drift (still 14 pip commands), and the "solution builds successfully" checkbox is checked, so the mechanical regeneration itself looks sound — the issues above are pre-existing generator behavior surfaced by this run, not new regressions from this specific diff.
• No prior review comments exist on this PR to reconcile against.

None of the above should be hand-patched in this generated-options PR; per repo policy they belong in tools/ModularPipelines.OptionsGenerator/, ideally as generic fixes (validation-expression builder, shared snapshot type, element-type-aware branch emission) rather than pip-specific special cases, followed by a fresh regeneration.

[thomhurst]

Replaces closed #5124 after source fix #5128 landed on main. Runtime coverage is in #5125 (633503d), which includes this exact generated output and adds single-use input regressions. Python Release build and all 20 local tests pass.

[thomhurst]

Superseded by merged #5125 (c241a09), which includes this exact generated output. Compared the full src/ModularPipelines.Python tree against this PR head (73126bd): no differences remain. Python tests and CI passed before merge. This replacement fulfilled the regeneration requested for #5124; no further pip output remains to apply.