release

Automating npm publishing and GitHub releases involves managing semantic version bumps, running tests, committing changes, creating Git tags, and pushing to remote repositories. This skill handles that entire pipeline end-to-end.

Bumping versions across configuration files before a Git tag release requires updating version numbers automatically based on semantic versioning. This skill detects the bump type and synchronizes the version updates before tagging.

Running tests before an npm deploy prevents release failures by executing automated test suites to verify code quality prior to version tagging and publishing, ensuring only validated code reaches the registry.

You can publish a specific semantic version like 2.4.0 directly. The skill accepts explicit version numbers alongside standard semantic versioning keywords such as patch or minor to initiate the release pipeline.

This automated release process does not require external dependencies to push Git tags. It operates independently to manage version bumping, Git tag creation, and remote repository pushing without additional packages.

Using an automated release pipeline instead of manually creating Git tags and publishing to npm ensures consistency across complex release steps and reduces manual error, streamlining the transition from code commit to public availability.