[Automated] Update flyway CLI Options

[thomhurst]

Summary

This PR contains automatically generated updates to flyway 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 minimal automated update PR — the only change is a timestamp bump in AssemblyInfo.Generated.cs:

-[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-03-01T03:14:14.2808687Z")]
+[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-03-08T03:10:47.5741980Z")]

Assessment: ✅ No issues found

The change is exactly what is expected for a scheduled automated flyway CLI options regeneration run. The generated timestamp correctly reflects the new run date (2026-03-08), and there are no changes to the actual options classes themselves — meaning the latest flyway CLI help output matches the existing generated code.

A few observations for general awareness:

1. No options drift detected: The fact that only the timestamp changed (and no options classes were modified) is a good signal — the flyway CLI interface hasn't changed since the last generation run on 2026-03-01. This is healthy.

2. Automation is working correctly: The PR was opened automatically, the solution built successfully, and auto-merge is enabled — the pipeline is functioning as intended.

3. Timestamp-only PRs could be suppressed: As a minor architectural suggestion (not a blocker), the generator could optionally skip opening a PR when only the timestamp changes and no actual option definitions differ. This would reduce noise in the PR list. This is purely a quality-of-life improvement and not a correctness concern.

This PR is safe to merge as-is.

[claude]

Code Review

Change Summary

This PR contains a single-line change in src/ModularPipelines.Flyway/AssemblyInfo.Generated.cs:

-[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-03-01T03:14:14.2808687Z")]
+[assembly: AssemblyMetadata("ModularPipelines.OptionsGenerator.GeneratedAt", "2026-03-15T03:15:23.2673415Z")]

Assessment: No issues found

This is a routine automated regeneration run. Only the GeneratedAt timestamp was updated — no options classes, enums, service interfaces, or implementation files changed. This is the expected outcome when the flyway CLI's help output is identical to the previously scraped version.

Observations

No CLI interface drift: The absence of any changes beyond the timestamp confirms that flyway's CLI has not introduced new commands, removed options, or changed flag names since the 2026-03-01 run. This is a healthy signal and validates that the automation is correctly detecting a stable interface.

Automation is functioning correctly: The generator ran, compared output, produced an identical options snapshot, updated the timestamp, opened this PR, verified the build, and enabled auto-merge — the full pipeline is operating as designed.

Minor improvement opportunity (non-blocking): With 30+ tool packages each running on a schedule, timestamp-only PRs like this one will accumulate regularly. The generator could be extended to skip PR creation when the only diff is the GeneratedAt metadata value. This would reduce noise without losing any safety guarantees, since a timestamp-only change carries no semantic information for consumers of the library. This is purely a quality-of-life consideration for repository maintainers.

This PR is safe to merge as-is.