wip-release

You can automate npm and GitHub package publishing by triggering a release pipeline that bumps versions, updates changelogs, commits changes, tags releases, and publishes packages automatically. This eliminates manual steps and potential errors across multi-platform publishing workflows.

The best way to update CHANGELOG.md and bump package.json versions is using an automated release pipeline. It synchronizes version bumps across project files and generates changelog entries, ensuring consistency between your documentation and published package state.

Yes, an automated release pipeline can create GitHub releases and tags for npm projects. The workflow commits version changes, applies Git tags, and generates detailed GitHub release notes alongside the npm publication.

Yes, this release automation supports multi-platform publishing. It publishes your project to both npm and GitHub Packages during the release process, handling the distribution to both registries simultaneously.

To publish a patch release with specific notes, you instruct your AI to perform a patch release with the desired notes, such as 'fix authentication bug'. The automation handles the version bump, changelog update, and publication.

You should not use an automated release pipeline if your project requires manual review of version bumps, custom pre-publish validation, or if it does not utilize standard npm or GitHub Packages workflows.