Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[changelog] Create and update CHANGELOG.md as separate file #461

Closed
aalmiray opened this issue Nov 2, 2021 · 11 comments
Closed

[changelog] Create and update CHANGELOG.md as separate file #461

aalmiray opened this issue Nov 2, 2021 · 11 comments
Assignees
Labels
enhancement New feature or request released Issue has been released
Milestone

Comments

@aalmiray
Copy link
Member

aalmiray commented Nov 2, 2021

Some projects prefer keeping a separate CHANGELOG.md file with all entries per release, instead of listing them in each release page.

@aalmiray aalmiray added the enhancement New feature or request label Nov 2, 2021
@aalmiray aalmiray self-assigned this Nov 2, 2021
@aalmiray aalmiray reopened this Nov 9, 2021
@aalmiray aalmiray removed their assignment Feb 11, 2022
@gotson
Copy link
Contributor

gotson commented Nov 16, 2022

@aalmiray i was wondering if there's any chance this would get done sooner rather than later ? I'm really interested in this, and that would help me migrate from semantic-release. I have an existing changelog that was generated by each release done with semantic-release, and i would like to keep that when migrating over to JReleaser.

Some examples:

I would be happy to just have the new changes generated by JReleaser to be prepended to the existing files, i don't need JReleaser to recreate the whole changelog since the beginning of times.

@aalmiray
Copy link
Member Author

I think the last hurdle is identifying a comment section that may be used to anchor the next entry.

@gotson
Copy link
Contributor

gotson commented Nov 16, 2022

In the examples above, the changelog for the newest version is always added at the top, so there wouldn't be any need for that, right ?

@aalmiray
Copy link
Member Author

Yes, but not all aggregated changelogs are equal. See https://github.com/helidon-io/helidon/blob/helidon-3.x/CHANGELOG.md

@gotson
Copy link
Contributor

gotson commented Nov 16, 2022

you're right, i agree. Do you actually need the anchor to ship the feature, or could it be done in 2 steps, first with append/prepend only, and later on have the anchoring feature?

@aalmiray
Copy link
Member Author

If there's no anchor then it will prepend. How about that?

@gotson
Copy link
Contributor

gotson commented Nov 16, 2022

If there's no anchor then it will prepend. How about that?

seems like a good default. I'm not sure about append, i don't think that's a thing.

@aalmiray aalmiray self-assigned this Nov 16, 2022
@aalmiray aalmiray added this to the v1.4.0 milestone Nov 16, 2022
aalmiray added a commit to jreleaser/jreleaser.github.io that referenced this issue Nov 16, 2022
aalmiray added a commit to jreleaser/jreleaser.github.io that referenced this issue Dec 2, 2022
aalmiray added a commit to jreleaser/jreleaser.github.io that referenced this issue Dec 13, 2022
@aalmiray aalmiray added the released Issue has been released label Dec 29, 2022
@aalmiray
Copy link
Member Author

@jacobk
Copy link

jacobk commented Mar 26, 2024

Hey! Sorry for reviving this old thread.

How is the appended changelog best incorporated into the release-process. I guess jreleaser won't add+commit+push the appended changelog as part of doing a full-release? But if not, how can one ensure that the updated changelog is part of the tagged commit?

@aalmiray
Copy link
Member Author

aalmiray commented Mar 26, 2024

You could configure a script hook (https://jreleaser.org/guide/latest/reference/hooks/script.html) to run on success, filtering by changelog. I'd recommend adding a condition (such as checking if running on CI or if the tool was not invoked in dryrun mode) as the hook would be invoked every time the changelog step successfully completes.

@jacobk
Copy link

jacobk commented Mar 26, 2024

You could configure a script hook (https://jreleaser.org/guide/latest/reference/hooks/script.html) to run on success, filtering by changelog. I'd recommend adding a condition (such as checking if running on CI or if the tool was not invoked in dryrun mode) as the hook would be invoked every time the changelog step successfully completes.

I see. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request released Issue has been released
Projects
None yet
Development

No branches or pull requests

3 participants