Release Candidates - Bug fixes in a trunk-based fashion

Hi team,
First of all, I want to give you kudos for maintaining this open-source project, which I really love 🙇

I have a couple of personal projects where I'm leveraging release-please while working in a trunk-based fashion.
Sometimes it happens that while working on a new release candidate, I spot some bugs before publishing it, and my current flow to fix those right now is:

- Fix the bug on the main trunk
- Release-please picks it up and adds it to the current release-candidate (awesome!)
- The changelog is updated, including the bugfix (this is because I usually mark those as fixes)

The last step is what I'm trying to prevent, because the bug wasn't in any previous release, and therefore has no value being communicated in the changelog.

On the other hand, I would still want to use `fix` conventional commit on the main trunk, to retain semantic meaning in the history.

So, how would you advise going about this?

Thank you! 🙏