[Automated] Update choco CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to choco 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

Assembly-wide public API impact

No active public API changes were detected in this assembly.

Command coverage

Command coverage report:

• choco (2.7.4): 27 commands, tree dbe8fe8a94432faaf1b5dd5f654b165f5722a9fd59318ccb9d8ce3681cafb72c
  • Baseline comparison: 27 commands at 2.7.4 -> 27 commands at 2.7.4

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 (1)

• src/ModularPipelines.Chocolatey/Generated/Choco.Generation.json 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: 100e88c3-efaf-4cb5-9001-1715eeee617b

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.}

[github-actions]

Review

This PR is a fully automated, mechanical update from ModularPipelines.OptionsGenerator, touching a single file:

• src/ModularPipelines.Chocolatey/Generated/Choco.Generation.json: only the generatorSourceSha256 field changes, from 773b4f9... to bdf2981....

This is the expected shape of change for this generator's freshness-tracking mechanism (scripts/Assert-GeneratedOptionsFreshness.ps1): each tool's *.Generation.json records a fingerprint of the generator's own source, and this PR simply re-stamps choco's snapshot to match the generator as it currently exists on main after the generator source changed. toolVersion and commandTreeSha256 are unchanged, so no actual CLI options/commands were regenerated for choco — this is purely a provenance-freshness bump, not a functional change.

I checked that other tools' Generation.json files still reference the older generator hash (773b4f9...), which is expected since this automation appears to run and land per-tool rather than repo-wide in one shot — each tool will pick up the new fingerprint independently as its own regeneration job runs.

No previous review comments exist to address (CodeRabbit explicitly skipped this file as generated/path-filtered). Per CLAUDE.md, generated options output should never be hand-edited, and this PR doesn't do that — it's produced by the generator itself.

Nothing actionable here — this is a clean, expected automated maintenance PR.

[github-actions]

Review

This PR is a fully automated, mechanical update from ModularPipelines.OptionsGenerator, touching a single file:

• src/ModularPipelines.Chocolatey/Generated/Choco.Generation.json: only the generatorSourceSha256 field changes, from 773b4f9... to 4f58359.... toolVersion (2.7.4) and commandTreeSha256 are unchanged, so no actual CLI options/commands were regenerated for choco — this is purely a provenance-freshness bump, not a functional change.

A previous automated review on an earlier commit of this same PR (head afac80d) already reached CLEAR for the same kind of change (a different generatorSourceSha256 value at that time). The generator source on main has apparently moved again since then, producing this new re-stamp on head 3caa51c — the shape of the change is identical and still expected per scripts/Assert-GeneratedOptionsFreshness.ps1's freshness-tracking mechanism.

Per CLAUDE.md, generated options output should never be hand-edited, and this PR doesn't do that — it's produced by the generator itself, and the file is correctly excluded from other review bots' path filters.

Nothing actionable here — this is a clean, expected automated maintenance PR.

[github-actions]

Review

This PR is a fully automated, mechanical update from ModularPipelines.OptionsGenerator, touching a single file:

• src/ModularPipelines.Chocolatey/Generated/Choco.Generation.json: only the generatorSourceSha256 field changes, from 773b4f9... to bccbb87.... toolVersion (2.7.4) and commandTreeSha256 are unchanged, so no actual CLI options/commands were regenerated for choco — this is purely a provenance-freshness bump, not a functional change.

This is the same PR reviewed twice before (heads afac80d and 3caa51c), both CLEAR. The generator source on main has moved again since, producing another re-stamp on the current head — the shape of the change is identical and still expected per scripts/Assert-GeneratedOptionsFreshness.ps1's freshness-tracking mechanism.

Per CLAUDE.md, generated options output should never be hand-edited, and this PR doesn't do that — it's produced by the generator itself, and the file is correctly excluded from other review bots' path filters.

Nothing actionable here — this is a clean, expected automated maintenance PR.

[github-actions]

Review

This PR is a fully automated, mechanical update from ModularPipelines.OptionsGenerator, touching a single file:

• src/ModularPipelines.Chocolatey/Generated/Choco.Generation.json: only the generatorSourceSha256 field changes, from 773b4f9... to b728fdf.... toolVersion (2.7.4) and commandTreeSha256 are unchanged, so no actual CLI options/commands were regenerated for choco — this is purely a provenance-freshness bump, not a functional change.

This is the same PR reviewed three times before (heads afac80d, 3caa51c, 06ffe7e), all CLEAR. The generator source on main has moved again since, producing another re-stamp on the current head — the shape of the change is identical and still expected per scripts/Assert-GeneratedOptionsFreshness.ps1's freshness-tracking mechanism.

Per CLAUDE.md, generated options output should never be hand-edited, and this PR doesn't do that — it's produced by the generator itself.

Nothing actionable here — this is a clean, expected automated maintenance PR.

[github-actions]

Review

This PR is a fully automated, mechanical update from ModularPipelines.OptionsGenerator, touching a single file:

• src/ModularPipelines.Chocolatey/Generated/Choco.Generation.json: only the generatorSourceSha256 field changes, from 773b4f9... to 856912a.... toolVersion (2.7.4) and commandTreeSha256 are unchanged, so no actual CLI options/commands were regenerated for choco — this is purely a provenance-freshness bump, not a functional change.

This is the same PR reviewed four times before (heads afac80d, 3caa51c, 06ffe7e, ae36f21), all CLEAR. The generator source on main has moved again since, producing another re-stamp on the current head — the shape of the change is identical and still expected per scripts/Assert-GeneratedOptionsFreshness.ps1's freshness-tracking mechanism.

Per CLAUDE.md, generated options output should never be hand-edited, and this PR doesn't do that — it's produced by the generator itself, and the file is correctly excluded from other review bots' path filters (CodeRabbit skipped it as generated).

Nothing actionable here — this is a clean, expected automated maintenance PR.