validate-and-ship

Pre-flight validation and shipping is automated by executing multi-phase workflows that handle plugin structure checks, frontmatter validation, artifact cleanup, and git operations sequentially. The process runs through phases with clear stop points when user intervention is required.

An automated plugin shipping pipeline includes branch creation, commit, push, pull request creation, and auto-review. These git operations execute in sequence after pre-flight validation and repository cleanup pass successfully.

Yes, you can run a dry-run to test plugin validation before shipping changes. Dry-run behavior is configurable via optional flags, allowing you to execute Phase 1-3 validation and cleanup steps without committing or pushing to git.

Validation checks performed on plugin repositories include structural validation, frontmatter checks, and convention verification. These pre-flight checks ensure repository hygiene and correctness before proceeding to branch creation and pull request submission.

Use automated pre-flight checks when your team needs repeatable, auditable validation and shipping for plugin releases. It reduces manual checks and potential errors in release workflows by guarding each step with clear stop points for blocking issues.

The shipping workflow stops and requires user intervention when blocking issues are detected during validation, cleanup, or git operations. These guarded stop points prevent shipping invalid plugin changes and ensure repository hygiene before proceeding.