[Automated] Update skopeo CLI Options

[thomhurst]

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

Assembly-wide public API impact

No active public API changes were detected in this assembly.

Command coverage

Command coverage report:

• skopeo (skopeo version 1.13.3): 11 commands, tree 71df545926b8f3395c60d1ed9e037569395c16b401bff0417eacdfb16d3d7908
  • Baseline comparison: 11 commands at skopeo version 1.13.3 -> 11 commands at skopeo version 1.13.3

Verification

• Solution builds successfully

---

🤖 Generated with ModularPipelines.OptionsGenerator

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-14T11:36:10.263481Z	bf3ede1	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

🗂️ Base branches to auto review (1)

• main

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: 27543034-78ec-42f6-8dfa-5c753321efc8

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.}

[greptile-apps]

Greptile Summary

The PR refreshes the Skopeo generation metadata to record the current generator source fingerprint. The Skopeo version and command-tree fingerprint remain unchanged, and no generated public API files are modified.

• Updates only generatorSourceSha256.
• Preserves the existing Skopeo tool version and command coverage fingerprint.

Confidence Score: 5/5

The PR appears safe to merge because it only refreshes generation provenance metadata and introduces no behavioral or public API change.

No actionable issues were identified; the updated checksum is consistent with a metadata-only regeneration while the tool version and command-tree fingerprint remain stable.

Important Files Changed

Filename	Overview
src/ModularPipelines.Skopeo/Generated/Skopeo.Generation.json	Updates the generator source checksum without changing the recorded CLI version, command tree, or generated API.

_{Reviews (2): Last reviewed commit: "chore: Update skopeo CLI options" | Re-trigger Greptile}

[github-actions]

Review

This PR contains a single-line, automated diff: it bumps generatorSourceSha256 in src/ModularPipelines.Skopeo/Generated/Skopeo.Generation.json from 50a6ccfc... to 8cfabb81....

• toolVersion (skopeo 1.13.3) and commandTreeSha256 are unchanged, so no scraped CLI surface changed.
• Only the recorded hash of the generator's own source changed, consistent with recent generic-logic changes to tools/ModularPipelines.OptionsGenerator/ (e.g. fix(generator): parse pnpm 12 clap-style help #4713). This is exactly the kind of generated provenance file the repo guidance says should never be hand-edited, and it hasn't been — the diff is the generator's own output.
• No hand-written code, no API surface, and no test changes are involved, so there's nothing to assess architecturally here.

No actionable findings. Looks good to merge.