build: release please changelog organization

[lwasser]

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]

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!!

[jdalrymple]

@lwasser Small questions - not a blocker though. These generally all look fine to me. We can refine it later if anything

[lwasser]

@lwasser Small questions - not a blocker though. These generally all look fine to me. We can refine it later if anything

Ok great - thanks!! I'll stop worrying about the docs/contributors updates. I realized in our changelogs for other projects, we always recognize new contributors. And once this new release is out the changelogs will be much smaller.

i'll work on a pr (this weekend?) that submits a build and deploy to npm. I think release, please can create a release as well, so I want to look into that next. And then we'll want to pause on pr's until the release but we aren't quite there yet.