File is update in the branch but not in the new release itself? #33
Description
Hi, I may be missing something obvious. I hope so because this is otherwise amazing!
When the github Action is triggered on release [published], the specified file is updated in the branch, but the file in the release itself still carries the previous version number. Is this on purpose?
Also this doesn't work as expected if using "github-flow"; i.e. a protected main branch and all changes are via pull request, and new Releases are tagged from main after merge.
If this isn't intended to work with my situation, that's totally cool, but hopefully I'm just doing it wrong?