Skip to content

Determine previous release commit for always-use-branch release Trains #108

@mp911de

Description

@mp911de

When releasing from a branch, we typically rebase these onto main to ensure we have included all previous changes. Rebasing breaks tags and so generating changelogs will include absent anchors in the comparison leading to duplicate changelog entries.

If we instead look for the release commit instead of release tag, we will have a much more predictable (and correct) outcome for determining the changelog.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions