Skip to content

build: release please changelog organization#455

Open
lwasser wants to merge 1 commit intoall-contributors:mainfrom
lwasser:release-please-types
Open

build: release please changelog organization#455
lwasser wants to merge 1 commit intoall-contributors:mainfrom
lwasser:release-please-types

Conversation

@lwasser
Copy link
Member

@lwasser lwasser commented Feb 22, 2026

When looking at how release please is setup, I noticed that it was ONLY including feat and fix related changes but i think we want to document all of the changes. We might consider modifying the pr "type" that the bot makes to remove those from the changelog as adding contributors is mostly noise in a development changelog. So let's review and think about what the changelog should look like.

NOTE: because there hasn't been a release in 3 years it's a very large changelog. most of them in the future after this will be small!

Please look here to see what the changelog will look like with this configuration. We can adjust as needed!

What:

The current changelog that it generates only has 2 commits and thinks it a minor release. but it's definitely NOT minor!

Why:

How:

Checklist:

  • Documentation
  • Tests
  • Ready to be merged
  • Added myself to contributors table

@lwasser lwasser force-pushed the release-please-types branch from fb76bea to 7c88028 Compare February 22, 2026 22:12
".": {
"changelog-path": "CHANGELOG.md",
"release-type": "node",
"changelog-sections": [
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the changelog mapping that it is using. We can modify as needed to make it look the way we want it to look ✨

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Because this is poorly documented in the google repo i'll try to document it more here.

@lwasser lwasser marked this pull request as ready for review February 22, 2026 22:15
@lwasser
Copy link
Member Author

lwasser commented Feb 25, 2026

Friends - we have superpowers now to customize the change log. If you all can, please have a look at this PR (there is no priority here on this one just a pr that i thought folks might have opinions on so we minus well discuss preferences now!

You can see what the changelog COULD look like using the configuration in this PR in the link below:

lwasser#10

ONE PROBLEM and we may just want to manually update the first iteration of the changelog. i don't think we want all of the all contributors bot pr's in that changelog as it adds uneeded noise. but i like having things like dependency updates and other fixes docs etc in the changelog just to document the development/release history.

We could fix all the contributors' PRs by customizing the bot's pr title that it creates (I think?), to filter future bot contributor pr's. OR we could edit the changelog before merging to remove them too.

I'd love any and all feedback on the sections and which conventional commit "types" i moved into which sections as that all can be customized through this pr! Thank you!!

chore: force config via json file
@lwasser lwasser force-pushed the release-please-types branch from f0c5ee5 to 8a6b208 Compare February 25, 2026 02:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant