Skip to content

Commit assigned to tag section instead of Unreleased section when merging a feature branch #188

@marcoalessandro

Description

@marcoalessandro

Describe the bug

A commit made in a separate branch on a date previous to the release tag is included in the tagged section instead of the Unreleased section. The merge happens after the initial tag of the release and the commit still ends up in the released section with the latest tag, instead of the Unreleased section.

To reproduce

  • Day 05/25/23 -> Branch feature/my-feature commit xyz
  • Day 05/29/23 -> Branch release/14.0 commit abc tagged 14.0.0
  • Day 05/30/23 -> Merge branch feature/my-feature into release/14.0

Expected behavior

Unreleased
  • Commit xyz
14.0.0
  • Commit abc

Observed behavior

14.0.0
  • Commit abc
  • Commit xyz

Additional context

Thank you in advance for the support, I will remain available for any other clarification or detail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions