hmem-release

Pre-publish release checks validate version bumps, builds, type checks, and test results before npm publish. Running this checklist confirms all release criteria are satisfied to prevent forgotten steps and release slips.

Before publishing an npm package, validate version bumps, run builds, execute type checks, and verify test results. You must also confirm skill audits, configuration updates, and changelog notes are synchronized with the release.

To ensure documentation is updated before an npm version bump, run a release readiness checklist that audits configuration updates, changelog notes, and documentation alignment across code and docs before publishing.

Automating release readiness validation for hmem-mcp involves running a checklist that verifies version bumps, type checking, skill audits, and migration steps. This automatically confirms all release criteria are satisfied before publishing.

Yes, you need to run type checks before bumping an npm package version. Release readiness validation requires type checking, builds, and test results to pass to prevent release slips and ensure code stability.

Skipping post-publish checks after an npm release risks missing configuration updates, changelog synchronization, and migration steps. Running the full release checklist ensures all criteria are satisfied and prevents forgotten steps.