Skip to content

docs: Improve release and breaking changes management #675

@aeneasr

Description

@aeneasr

Instead of manually writing release notes for HISTORY.md, the file should be renamed to UPGRADE.md and contain only mission-critical information on how to upgrade between versions.

Introduce an automatically generated CHANGELOG.md which contains a full list of changes.

Metadata

Metadata

Assignees

No one assigned

    Labels

    featNew feature or request.

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions