bmad-os-release-module

You can automate the npm module release process by coordinating changelog drafting, version bumps, git tagging, npm publishing, and GitHub release creation in a single workflow to reduce manual toil and human error.

Automating version bumps and changelog updates involves validating the project state, prompting for changelog entries to ensure release readiness, and then applying standard npm versioning practices alongside git tag creation.

Yes, you can coordinate npm publishing and GitHub release creation in one automated step, ensuring that your published npm library version matches the corresponding GitHub release and git tag.

Yes, drafting a changelog entry is required before publishing; the automation validates your project state and prompts for a changelog entry to ensure your library is fully ready for release.

Yes, this workflow applies to projects that publish libraries to npm and follow changelog-driven release cycles, covering standard npm release practices for repositories hosted on GitHub.

If your project state is not ready, the release automation validates the repository and prompts you to resolve missing changelog entries or other release readiness requirements before proceeding with the version bump.