[Automated] Update winget CLI Options

[thomhurst]

Summary

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

• winget (v1.29.290): 42 commands, tree be6725b4f2522a990030007897738ac016f66f7f5ce700a730ea0a50070fb1bb
  • Baseline comparison: 42 commands at v1.29.290 -> 42 commands at v1.29.290

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.WinGet/Generated/Winget.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: c3273346-544a-4ead-becb-6ce98928e6c4

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 update with a trivial, metadata-only diff: the sole change is to generatorSourceSha256 in src/ModularPipelines.WinGet/Generated/Winget.Generation.json, recording that the generator's own source hash changed. The toolVersion (v1.29.290), commandTreeSha256, and command count (42) are all unchanged, meaning no generated options classes, public API, or behavior actually changed for this run.

No actionable findings — nothing to flag architecturally or otherwise, since there's no logic in this diff to evaluate.

[github-actions]

Review

This PR contains a single, mechanical change: a bump to generatorSourceSha256 in src/ModularPipelines.WinGet/Generated/Winget.Generation.json (1 file, +1/-1).

Verified details:

• toolName, toolVersion (v1.29.290), and commandTreeSha256 are all unchanged — the winget command tree itself did not change.
• generatorSourceSha256 is a fingerprint of the OptionsGenerator's own source tree (produced by Get-GeneratedOptionsSourceFingerprint / Write-GeneratedOptionsProvenance.ps1), independent of the tool's command tree. This value legitimately changes whenever the generator's source changes elsewhere on main, even if this package's generated output is otherwise identical.
• Both the old and new hashes are well-formed 64-character lowercase hex strings, matching the ^[a-f0-9]{64}$ pattern required by Assert-GeneratedOptionsFreshness.ps1.
• No hand-edited generated options/command classes, no generator logic, and no test code are touched, consistent with this repo's rule to never hand-edit generated output and to only update it via regeneration.

No actionable issues found — this is a routine provenance metadata update.

[github-actions]

Review

This PR is another automated, metadata-only update: the sole change is to generatorSourceSha256 in src/ModularPipelines.WinGet/Generated/Winget.Generation.json (1 file, +1/-1).

Verified:

• toolName (winget), toolVersion (v1.29.290), and commandTreeSha256 are all unchanged — the winget command tree did not change, so no generated options classes or public API actually changed.
• generatorSourceSha256 is a fingerprint of the OptionsGenerator's own source, independent of the tool's command tree, so it can legitimately bump on its own even with an identical command tree.
• Both hashes are well-formed 64-character lowercase hex strings.
• No hand-edited generated code, generator logic, or test files are touched — consistent with the repo rule to only change generated output via regeneration.

This is the same shape of change as the previous two automated PRs on this file, both of which were reviewed clean. No actionable findings here either.