[sbrunner]

Summary

With create-release: false, the changelog module never creates a release.

Context

Only the tag creation event was guarded by the create-release option. The changelog generation flow (triggered by the release, pull_request, milestone and discussion events) called _create_release unconditionally when no release existed for the tag, or when the release was deleted between the get and the update. For example, editing a milestoned closed pull request of a tag without a release created one even with create-release: false.

Implementation Details

• Changelog.process reads create-release (default configuration.CREATE_RELEASE_DEFAULT) in the changelog generation path and skips the release creation, with a log, when the option is disabled.
• The existing releases still get their changelog body updated, whatever the option value.

Impact/Risks

• No configuration change, no migration. Only the repositories with create-release: false are affected: they stop getting unexpected releases.