changelog-manager

You can automate changelog generation and version bumping by analyzing uncommitted git changes to compute the appropriate major, minor, or patch bump. The skill then updates CHANGELOG.md, synchronizes package versions, and prepares the GitHub release.

Automated release management synchronizes versions by reading the computed version bump and directly updating package.json and composer.json. It also refreshes README badges to ensure all version references across the project remain consistent.

The best way to prepare a GitHub release from uncommitted changes is to trigger an automated workflow that analyzes your current work, proposes a version bump, composes a thorough commit message, and optionally pushes a public Git tag to the remote repository.

Yes, you can use this release automation workflow for both Node.js and PHP projects because it explicitly synchronizes version numbers across package.json and composer.json, ensuring compatibility across both ecosystems.

You should not use automated changelog management for private repositories if you require public Git tags, as the tagging feature is optional and primarily designed for public repo workflows.

Your automated release workflow updates README badges during versioning to maintain documentation accuracy. It ensures that any version references displayed in your README reflect the newly synchronized package version after the bump.