Skip to content

Commits duplicate under new release versions in CHANGELOG.md #86

@fireflysemantics

Description

@fireflysemantics

Did a detailed writeup here.

https://stackoverflow.com/questions/78196255/get-release-it-to-put-each-new-commit-under-the-corresponding-release-version-in

This is what is happening:

## 1.2.0 (2024-03-20)


### Features

* add commit linting 5eee5b0
* add release it changelog generation 80e627c

## 1.1.0 (2024-03-20)


### Features

* add release it changelog generation 80e627c

When the CHANGELOG.md is regenerated with new version numbers, previous commits are also rendered under the new version number, in addition to being rendered where they were previously.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions