[Automated] Update pnpm CLI Options

[thomhurst]

Summary

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

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[claude]

Code Review - Automated pnpm CLI Options Update

This is an auto-generated PR updating pnpm CLI options classes. The changes are minimal (3 lines changed) and consist of:

Changes Reviewed

1. AssemblyInfo.Generated.cs - Timestamp update
Routine metadata update reflecting the new generation date. No concerns.

2. PnpmAuditOptions.Generated.cs - Documentation fix for --ignore-registry-errors
The description was corrected from:

"A build should fail because the registry has issues."

to:

"A build should not fail because the registry has issues."

This is a meaningful fix. The original description was logically contradictory — --ignore-registry-errors is designed to prevent build failures caused by registry outages, so the corrected description now accurately reflects the flag's intent. Good catch.

3. PnpmWhyOptions.Generated.cs - Description accuracy for --depth
Updated from "Max display depth of the dependency graph" to "Max display depth of the reverse dependency tree". This is more accurate since pnpm why shows reverse dependencies (i.e., why a package is installed), not a forward dependency graph.

Overall Assessment

All changes are generated (as expected per CLAUDE.md), correct, and improve documentation accuracy. The semantic fix in PnpmAuditOptions is particularly valuable as it removes a misleading description that contradicted the flag's purpose. No architectural concerns.

✅ Approved.

[claude]

Code Review - Automated pnpm CLI Options Update (Updated)

This is an auto-generated PR updating pnpm CLI options classes. The previous review was dismissed — this updated review covers all current changes.

Changes Reviewed

1. AssemblyInfo.Generated.cs — Timestamp update
Routine metadata update reflecting the new generation date (2026-03-08). No concerns.

2. PnpmAuditOptions.Generated.cs — Documentation fix for --ignore-registry-errors
(Previously reviewed and approved)
Corrects a logically contradictory description. The fix now accurately communicates that the flag prevents build failures due to registry outages. Good fix.

3. PnpmWhyOptions.Generated.cs — Description accuracy for --depth
(Previously reviewed and approved)
Improved from "dependency graph" to "reverse dependency tree", which better reflects that pnpm why shows reverse dependencies.

4. --filter ShortForm -F added across multiple options classes (NEW)

The following files now include ShortForm = "-F" on the --filter CLI option:

• PnpmAddOptions.Generated.cs
• PnpmPublishOptions.Generated.cs
• PnpmRunOptions.Generated.cs
• PnpmWhyOptions.Generated.cs

This is accurate — pnpm does support -F as the short form of --filter (verified in pnpm docs). Exposing this via ShortForm lets users use the terser flag syntax through the strongly-typed API, which is a meaningful usability improvement for workspace-heavy setups.

Overall Assessment

All changes are auto-generated (as expected per CLAUDE.md), correct, and improve accuracy and usability. The ShortForm = "-F" additions are a legitimate enhancement that align the wrapper with the underlying CLI. No architectural concerns.

✅ Approved.

[claude]

Code Review - Automated pnpm CLI Options Update (2026-03-15)

Previous reviews were posted on 2026-03-01 and 2026-03-08. All substantive changes have already been reviewed and approved. This review confirms there are no new changes beyond the timestamp update.

Changes Since Last Review

AssemblyInfo.Generated.cs — Timestamp update only
Generation timestamp moved from 2026-03-08 to 2026-03-15. Routine scheduled re-run of the generator with no code changes.

Previously Reviewed Changes (still present, no issues)

All previously approved changes remain in place:

• ✅ PnpmAuditOptions doc fix: "should not fail" — corrects a logically contradictory description
• ✅ PnpmWhyOptions --depth description: "reverse dependency tree" — more precise for pnpm why
• ✅ ShortForm = "-F" on --filter across PnpmAddOptions, PnpmPublishOptions, PnpmRunOptions, PnpmWhyOptions — accurate and improves usability

Overall Assessment

No new concerns. This is a clean re-generation that inherits all prior approved improvements. The generator is working correctly.

✅ Approved.

[claude]

Code Review

This is a clean automated regeneration of pnpm CLI options. The changes are small but meaningful.

Changes Summary

Short form flag addition () — , , , ,

Correctly reflects that pnpm's --filter flag accepts -F as a short form. This is a useful addition that allows users of these options to pass the short flag variant.

Documentation fix in PnpmAuditOptions

The original description for --ignore-registry-errors was:

"A build should fail because the registry has issues."

Updated to:

"A build should not fail because the registry has issues."

This corrects a significant logical error in the docs — the original text was the opposite of the flag's intent. --ignore-registry-errors is designed to prevent build failures when the registry has problems, so the "not" is semantically critical.

Description precision fix in PnpmWhyOptions

"Max display depth of the dependency graph" → "Max display depth of the reverse dependency tree"

This is more accurate — pnpm why specifically shows the reverse dependency tree (why something was installed), not a generic forward dependency graph.

Assessment

The changes are correct, well-scoped, and the generator is doing exactly what it should — keeping options classes in sync with the actual CLI. The documentation correction for --ignore-registry-errors is particularly valuable as the original description was misleading.

No issues found. LGTM.

[claude]

Code Review

This is a clean automated regeneration of pnpm CLI options. The changes are small but meaningful.

Changes Summary

Short form flag addition (ShortForm = "-F") — PnpmAddOptions, PnpmPublishOptions, PnpmRunOptions, PnpmWhyOptions

Correctly reflects that pnpm's --filter flag accepts -F as a short form. This is a useful addition that allows users of these options to pass the short flag variant.

Documentation fix in PnpmAuditOptions

The original description for --ignore-registry-errors was:

"A build should fail because the registry has issues."

Updated to:

"A build should not fail because the registry has issues."

This corrects a significant logical error in the docs — the original text was the opposite of the flag's intent. --ignore-registry-errors is designed to prevent build failures when the registry has problems, so the "not" is semantically critical here.

Description precision fix in PnpmWhyOptions

"Max display depth of the dependency graph" → "Max display depth of the reverse dependency tree"

This is more accurate — pnpm why specifically shows the reverse dependency tree (why something was installed), not a generic forward dependency graph.

Assessment

The changes are correct, well-scoped, and the generator is doing exactly what it should — keeping options classes in sync with the actual CLI. The documentation correction for --ignore-registry-errors is particularly valuable as the original description was misleading (negation was missing, inverting the meaning).

No issues found. LGTM.

[claude]

Automated pnpm CLI Options Update - Review

This is a clean, minimal automated update that correctly reflects the latest pnpm CLI documentation. No architectural or design concerns.

Changes Summary

Short form alias added (-F for --filter) - Applied consistently across all 4 affected options classes (PnpmAddOptions, PnpmPublishOptions, PnpmRunOptions, PnpmWhyOptions). This is a good improvement as it allows users of the library to use the short-form flag when building CLI commands.

Documentation fix in PnpmAuditOptions - The --ignore-registry-errors description was corrected from "A build should fail because the registry has issues" to "A build should not fail because the registry has issues." This is a meaningful correction — the original text contradicted the intent of the flag (the option exists precisely so that registry errors do NOT fail the build).

Documentation fix in PnpmWhyOptions - The --depth description was updated from "Max display depth of the dependency graph" to "Max display depth of the reverse dependency tree." This is more accurate since pnpm why specifically shows the reverse dependency tree (i.e., why a package is installed), not a general dependency graph.

Timestamp update - Reflects the regeneration date, as expected.

Assessment

The changes are well-scoped, consistent, and accurately reflect upstream pnpm CLI changes. The documentation corrections are particularly valuable as they fix a misleading description. No issues found.

[claude]

This is an automated update to the pnpm CLI options classes, and the changes look correct and accurate.

Summary of changes:

1. Short form flag added for --filter (-F) in PnpmAddOptions, PnpmPublishOptions, PnpmRunOptions, and PnpmWhyOptions - This correctly reflects the pnpm CLI's support for -F as a shorthand for --filter, which is consistent across all subcommands that support filtering.

2. Documentation fix in PnpmAuditOptions - The --ignore-registry-errors description was corrected from "A build should fail because the registry has issues" to "A build should not fail because the registry has issues". This was a logical inversion in the original text - the --ignore-registry-errors flag is specifically designed to prevent build failure when the registry has issues, so the corrected documentation accurately reflects the flag's intent.

3. Documentation fix in PnpmWhyOptions - The --depth description was updated from "Max display depth of the dependency graph" to "Max display depth of the reverse dependency tree". This is accurate since pnpm why shows the reverse dependency tree (what depends on a package), not the forward dependency graph.

4. Timestamp update in AssemblyInfo.Generated.cs reflecting when the generation occurred.

All changes are consistent with the generated file pattern (files have .Generated.cs suffix and [ExcludeFromCodeCoverage] attributes). The documentation corrections in particular are meaningful improvements - the --ignore-registry-errors fix corrects a logical inversion that could have confused users about the flag's behavior.

No issues found. This PR is straightforward and safe to merge.

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

🟢 Metrics 0 complexity

Metric	Results
Complexity	✅ 0 (≤ 20 complexity)

View in Codacy

_{TIP This summary will be updated as you push new changes. Give us feedback}

[claude]

Code Review - Automated pnpm CLI Options Update (2026-04-12)

This is another scheduled regeneration. The only change from the previous review (2026-04-05) is the generation timestamp update.

Change Since Last Review

AssemblyInfo.Generated.cs — Timestamp update only
Generation timestamp updated from 2026-04-05T03:... to 2026-04-12T03:34:21. Routine scheduled re-run with no code changes.

Previously Reviewed Changes (still present, no new issues)

All substantive changes have been reviewed and approved across prior iterations:

• ✅ ShortForm = "-F" on --filter across PnpmAddOptions, PnpmPublishOptions, PnpmRunOptions, PnpmWhyOptions — accurate short form alias for pnpm's -F flag
• ✅ PnpmAuditOptions doc fix: "should not fail" — corrects a logical inversion in the original description
• ✅ PnpmWhyOptions --depth description: "reverse dependency tree" — more precise for pnpm why

Assessment

The generator is running correctly and producing clean output. No new changes, no new concerns. Safe to merge.

[claude]

Code Review - Automated pnpm CLI Options Update (2026-04-19)

This is a scheduled regeneration. Compared to the previous review (2026-04-12), there is one meaningful new change.

New Change Since Last Review

#nullable enable added to all generated files

The following files now include #nullable enable at the top:

• PnpmAddOptions.Generated.cs
• PnpmAuditOptions.Generated.cs
• PnpmCreateOptions.Generated.cs
• PnpmDlxOptions.Generated.cs
• PnpmInitOptions.Generated.cs
• PnpmOptions.Generated.cs
• PnpmPublishOptions.Generated.cs
• PnpmRunOptions.Generated.cs
• PnpmUnlinkOptions.Generated.cs
• PnpmWhyOptions.Generated.cs
• IPnpm.Generated.cs
• Pnpm.Generated.cs

This is a good improvement. Enabling nullable reference types at the file level ensures that null-safety is enforced consistently for these options classes, surfacing potential null dereferences at compile time for consumers. It aligns with modern C# best practices and is consistent with how the rest of the codebase should handle nullability. The existing string? annotations on option properties already anticipated this — the #nullable enable directive makes those annotations authoritative rather than advisory.

Previously Reviewed Changes (still present, no new issues)

• ✅ ShortForm = "-F" on --filter across PnpmAddOptions, PnpmPublishOptions, PnpmRunOptions, PnpmWhyOptions
• ✅ PnpmAuditOptions doc fix: "should not fail" — corrects a logical inversion
• ✅ PnpmWhyOptions --depth description: "reverse dependency tree" — more precise for pnpm why

Assessment

Clean, well-scoped update. The #nullable enable addition is a meaningful improvement to the generator's output. No issues found. LGTM.