[Automated] Update newman CLI Options

[thomhurst]

Summary

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

This is a fully automated PR regenerating the Newman CLI options. The only change is the timestamp in AssemblyInfo.Generated.cs — the actual options classes are unchanged.

Observation: Timestamp-Only PRs Add Noise

The generator ran, found no changes to the actual options, but still opened this PR because the GeneratedAt timestamp advanced. This creates a maintenance burden: reviewers see a PR, evaluate it, and auto-merge it, only to discover the sole change is a timestamp. Over time, these accumulate and dilute signal from PRs that contain real option updates.

Suggested improvement: In the OptionsGenerator, before writing AssemblyInfo.Generated.cs, compare the newly-generated options output against the currently-committed files. If the only delta is the timestamp field, skip creating/pushing the PR entirely (or at minimum skip updating the timestamp). This way PRs in this label series always carry a substantive change.

Alternatively, if the intent is specifically to track that the generator ran and confirmed no changes, consider a CI check or run-log rather than a pull request.

On the change itself

The timestamp bump is correct and harmless. No functional risk.

Verdict: Safe to merge as-is, but worth addressing the generator logic to suppress no-op PRs.

[claude]

Code Review

This is a fully automated PR regenerating the Newman CLI options. The only change is the GeneratedAt timestamp in AssemblyInfo.Generated.cs — the actual options classes are unchanged.

Observation: Timestamp-Only PRs Add Noise

The generator ran, found no changes to the actual options, but still opened this PR because the GeneratedAt timestamp advanced. This creates a maintenance burden: reviewers see a PR, evaluate it, and auto-merge it, only to discover the sole change is a timestamp. Over time these accumulate and dilute signal from PRs that contain real option updates.

Suggested improvement: In the OptionsGenerator, before writing AssemblyInfo.Generated.cs, compare the newly-generated options output against the currently-committed files. If the only delta is the timestamp field, skip creating/pushing the PR entirely (or at minimum skip updating the timestamp). This way PRs in this label series always carry a substantive change.

Alternatively, if the intent is specifically to track that the generator ran and confirmed no changes, consider a CI status check or a run log rather than a pull request.

On the change itself

The timestamp bump is correct and harmless. No functional risk.

Verdict: Safe to merge as-is, but worth addressing the generator logic to suppress no-op PRs.

[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

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}