I have two actions set up in my Foundry module that are working well. Both are based on patterns in regular use by the Foundry community developers on the Foundry Discord - which is where I learned the approach, though I've made adjustments to tighten the permissions allowed to the actions to the bare minimum required. Both should adapt easily to this project.

The first action runs when a PR is merged to main, updating the draft release change notes from the PR title and label. I can't edit your labels. If the setup needs any changes they will be very minimal, and I'll note them in the PR description. The advantage of this workflow over others I looked at is that it uses the PR title instead of the commit messages. This avoids filling the notes with fine-grained noise. The action can also run manually (another of my tweaks), so PR labels or titles can be changed after merging but before the release is published to update the notes.

The second action runs when a release is being made. It updates the manifest (system.json) based on the commit tag for the release, builds the release artifacts and attaches them. No more manual edits to the manifest. Though with my setup you still need to manually create the new release on Foundry, though I am looking into automating that as well with cURL AxiosJS. No idea when that will be done though! This is a hobby after all, not my day job.