eforge-release

To automate a GitHub release, you specify a release type argument like patch, minor, or major, and the workflow generates notes from git history, updates CHANGELOG.md, and publishes the release.

Generating release notes from git commit history is handled automatically by parsing commit logs to create traceable notes, which are then appended to the CHANGELOG.md file during the release process.

You can enforce semantic versioning by passing specific arguments for patch, minor, or major releases, which triggers a deterministic version bump and updates the project versioning accordingly.

Yes, the automated release workflow checks git status before committing changes to ensure a clean working directory, preventing accidental inclusion of untracked files in the release commit and tag.

Yes, you can update CHANGELOG.md automatically during a version release by generating new entries from the git commit history and appending them to the changelog file alongside the new version bump.

The best way to create an annotated GitHub release with generated notes is to use an end-to-end release workflow that commits version changes, pushes the tag, and publishes the release with tracked commit notes.