Skip to content

configure changelog.md.j2 to have only final releases in the generated changelog.md #837

Closed

Description

@intex46

Python version: 3.10
python_semantic_release==8.5.2

Hello, can you provide me an example of changelog.md.j2 in order to include changes made in pre-releases and alpha-releases in the final release section

Actual Changelog.md:

# CHANGELOG

v0.2.1 (2024-02-14)
Chore
chore(release): release v0.2.1 [skip ci]
v0.2.1-rc.1 (2024-02-14)
Build
build: blablablah
Ci
ci: blablablah
Fix
fix: fix bug1 and bug2
v0.2.0 (2024-02-13)

The desired Changelog.md:

# CHANGELOG

v0.2.1 (2024-02-14)
Chore
chore(release): release v0.2.1 [skip ci]
Build
build: blablablah
Ci
ci: blablablah
Fix
fix: fix bug1 and bug2
v0.2.0 (2024-02-13)

Activity

  1. codejedi365 commented on Feb 15, 2024

    @codejedi365
    Contributor

    I don't believe this is doable easily from a template. You would likely have to write a fairly complex jinja macro to accomplish this.

    I do believe this is a duplicate of a recent request, #817. I have not had the cycles to put towards this idea yet although I fully agree it should be the default.

  2. intex46 commented on Feb 16, 2024

    @intex46
    Author

    hello, thanks for your feedback, is it a new feature to consider ?

  3. codejedi365 commented on Feb 17, 2024

    @codejedi365
    Contributor

    Yes, when I finish with the current multi branch bugs, I will implement something like this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

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