gspdev-publish

You can automate npm release publishing by bumping version numbers, updating the changelog, running audit scripts, and creating GitHub releases. This process validates code, formats documentation, and prompts you to run npm publish after all checks pass.

Updating a changelog and bumping versions involves modifying both the VERSION file and package.json, then promoting the unreleased changelog section to a versioned entry. This ensures documentation and version numbers stay synchronized before publishing.

Yes, version bumping can automatically open a PR, merge it, create a GitHub release, and close the associated milestone. This streamlines the release cycle by connecting git operations directly to GitHub project management.

Yes, the release process runs the project's audit script and aborts on failures before creating a GitHub release. This enforces code validation early, preventing broken versions from being tagged or published to npm.

Formatting an unreleased changelog requires populating the pending section, promoting it to a versioned entry, and generating a site MDX file. This translates raw git changes into structured documentation for the target release.

The automated release pipeline prompts for npm publish to ensure user confirmation before the final deployment. This manual checkpoint prevents accidental pushes to the npm registry after all automated git and GitHub checks pass.