release-manager

You validate a Homebridge plugin release by running a full release checklist that executes builds, tests, and lint in order, stopping on the first blocking failure. This provides a clear pass or fail verdict before semantic-release runs.

Dev-to-beta and dev-to-latest promotions require build, test, lint, version-placeholder, README, schema alignment, and conventional-commit checks to pass. The review explicitly reports any blocking failures to ensure documentation and schema definitions do not drift out of sync.

Semantic-release can fail when documentation and schema drift because release readiness requires README and config schema alignment. Running a pre-release review catches stale future-feature wording and schema mismatches before the automated release process takes over.

Yes, you can gate releases by enforcing conventional commit compliance as part of a pre-release validation checklist. This verifies commit messages meet standards alongside build, test, and lint checks before allowing a dev-to-latest promotion to proceed.

You need to audit README and config schema alignment when preparing a promotion pull request for your Homebridge plugin. This audit checks for stale future-feature wording and schema mismatches, ensuring documentation accuracy before semantic-release executes.