Description
PictoPy currently does not maintain a repository-wide changelog, making it difficult to track changes across releases. In addition, releases can be created without verifying that the corresponding changelog entry exists.
Proposed Solution
Add a CHANGELOG.md following the Keep a Changelog format and introduce a release validation step in CI.
The validation should ensure that a changelog entry exists for the version being released before the release process can continue.
This builds on the version synchronization workflow introduced in #1306
Benefits
Provides a centralized history of project changes.
Improves release consistency.
Prevents releases from being published without changelog updates.
Description
PictoPy currently does not maintain a repository-wide changelog, making it difficult to track changes across releases. In addition, releases can be created without verifying that the corresponding changelog entry exists.
Proposed Solution
Add a
CHANGELOG.mdfollowing the Keep a Changelog format and introduce a release validation step in CI.The validation should ensure that a changelog entry exists for the version being released before the release process can continue.
This builds on the version synchronization workflow introduced in #1306
Benefits
Provides a centralized history of project changes.
Improves release consistency.
Prevents releases from being published without changelog updates.