h4tcher-release-prep

Automate changelog formatting and versioning by orchestrating package.json, plugin manifests, and lockfile refreshes to a single semver source of truth. This enforces Keep-a-Changelog section formatting for reliable CI extraction during npm package releases.

Verify adapter registry completeness by running release fidelity checks that validate adapter registration and capability matrices. This ensures all adapters are properly documented and registered before publishing to npm or creating GitHub release notes.

Enforce documentation parity by building the Docusaurus website with strict broken-link failure behavior. This verifies inventory parity against governance counts and sidebars, ensuring published docs match repository changes exactly.

Reconcile merged PRs with the changelog by enforcing release fidelity checks that verify all merged PRs are represented in CHANGELOG.md. Unrepresented PRs must be explicitly classified before the release workflow can proceed.

Yes, you can run lockfile and supply chain auditing alongside CI validation. The release workflow coordinates tests, typecheck, lint, and build processes together to ensure the published package meets strict technical supply chain requirements.

CI pipelines fail extracting release notes when the changelog lacks strict Keep-a-Changelog section formatting. Applying a coordinated release-prep workflow enforces the required formatting structure, enabling reliable automated extraction for GitHub release notes.