Skip to content

[Automated] Update skopeo CLI Options#2411

Open
thomhurst wants to merge 1 commit intomainfrom
automated/update-cli-options-skopeo
Open

[Automated] Update skopeo CLI Options#2411
thomhurst wants to merge 1 commit intomainfrom
automated/update-cli-options-skopeo

Conversation

@thomhurst
Copy link
Owner

Summary

This PR contains automatically generated updates to skopeo 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 Feb 22, 2026
@thomhurst thomhurst enabled auto-merge (squash) February 22, 2026 03:11
@thomhurst thomhurst force-pushed the automated/update-cli-options-skopeo branch from 5625da6 to 47ad7a3 Compare March 1, 2026 03:13
Copy link

@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 a minimal automated PR — the only actual change is a timestamp update in AssemblyInfo.Generated.cs:

  • ModularPipelines.OptionsGenerator.GeneratedAt updated from 2026-02-15T03:12:102026-03-01T03:12:30

Observations

No options changes detected: Despite the PR description mentioning "Updated options classes to reflect latest CLI documentation", the diff shows only a timestamp change. This means the skopeo CLI scraped today produced identical options to the version from Feb 15. This is expected if skopeo hasn't released a new version in that period — the generator ran, found no differences, and only the "GeneratedAt" metadata was updated.

Automated process is working correctly: The generator correctly reflects that it ran and checked the tool, even when no substantive changes were needed. This is good hygiene for tracking when the last check was performed.

Verdict

Approved — no issues. The change is correct and expected for an automated options-generation PR where the CLI hasn't changed. The timestamp serves as a useful audit trail confirming the generator was run against the current tool version.

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