Skip to content

[Automated] Update helm CLI Options#2632

Open
thomhurst wants to merge 1 commit into
mainfrom
automated/update-cli-options-helm
Open

[Automated] Update helm CLI Options#2632
thomhurst wants to merge 1 commit into
mainfrom
automated/update-cli-options-helm

Conversation

@thomhurst
Copy link
Copy Markdown
Owner

Summary

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

@thomhurst thomhurst added automated dependencies Pull requests that update a dependency file labels May 17, 2026
@thomhurst thomhurst enabled auto-merge (squash) May 17, 2026 03:20
Copy link
Copy Markdown

@claude claude Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This is an automated PR that updates the Helm CLI options classes via the ModularPipelines.OptionsGenerator generator.

What Changed

The diff contains a single change: a timestamp bump in src/ModularPipelines.Helm/AssemblyInfo.Generated.cs:

-[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-05-10T03:18:05.7733164Z")]
+[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-05-17T03:19:05.1827906Z")]

No options classes were added, removed, or modified — the generator ran and found no differences in the Helm CLI output since the last generation (2026-05-10), so only the timestamp was updated.

Assessment

This is fine. Periodically re-running the generator and recording the new timestamp even when there are no functional changes is a reasonable approach — it proves the generator ran successfully against the current tool version and the CLI surface hasn't changed.

Minor Observation

If the intent is to track meaningful changes to CLI options, it may be worth considering whether a no-op run (timestamp-only diff) should produce a PR at all. Skipping PRs when the only change is the timestamp would reduce automation noise. This is not a blocker — just something to consider for the generator's CI configuration.

@codacy-production
Copy link
Copy Markdown

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

automated dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant