Regenerate release notes on release updates

[rantoniuk]

Fixes #474

@ncipollo:

1. I'm not sure why the dist/* is part of the repo, since the build/release should be out of here. Let me know if you what me to remove dist/* from the PR (but I had to have it for testing - yes, it works ;-) ).
2. The logic is so complicated that I didn't know if I should use omitBodyDuringUpdate somewhere or not and what to do in case someone sets body explicitly.
3. yarn release is not working, since it's depending on ncc (not in deps) and ts-node that is not in --production.

[ncipollo]

Thanks for the PR! Had a few questions and change requests.

[ncipollo]

Sorry - would you mind rebasing now 😅. I think it's a good idea to add formatting rules to the project, but I wanted to split that out from this change. I checked in the biome rules on main and ran the formatter. For some reason there are some conflicts, even though I copied the biome file from this branch.

[rantoniuk]

Done. Still, the yarn release command is broken, it will not run in --production mode with the current package.json setup:

$ rm -rf node_modules

$ yarn release
yarn run v1.22.22
$ yarn clean && yarn install --production && yarn build && yarn package
$ rm -rf lib/*
[1/5] 🔍  Validating package.json...
[2/5] 🔍  Resolving packages...
[3/5] 🚚  Fetching packages...
[4/5] 🔗  Linking dependencies...
[5/5] 🔨  Building fresh packages...
$ tsc
/bin/sh: tsc: command not found
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed with exit code 127.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

Yes, you guessed correctly, the dist/ in this PR is not built using --production but a standard yarn install from development mode after running yarn test.

(before you say: try doing npm install -g typescript - no, global installations are the wrong way to go and they will cause problems when working on multiple projects with different TS versions. That's why npx was created for or rollup like in the parent repo )

[rantoniuk]

Thanks for triggering the tests! Do you need anything else?

[ncipollo]

Looks great 🎉. Thank you for bearing with me through my PR feedback haha. Thanks for this contribution!!

[rantoniuk]

@ncipollo I guess you still need to re-push @v1 for this to be visible via ncipollo/release-action@v1 ?

[ncipollo]

Yeah I need push the next minor tag and then update v1 to point to that. I will get to that this weekend.