This is always an interesting problem to tackle. IMO automatic releases on a push to the default branch are overly chatty. A middle-ground I've used in the past is to cut a new release when a new tag is created.
I wrote this action a couple of years ago to do just that. After a tag is applied, GitHub updates all the relevant bits of the repo to have the correct version from the tag, pushes that to main, and then force pushes the tag to the new hash that it created. After that's done, it builds the project and releases it to NuGet. NOTE: this can be a pretty low priority, even if NuGet releases through the UI can be a manual process, they're really straight-forward to do.
I wrote the parallel action for maven releases: which I found much more valuable because releasing through sonatype is such a bigger PITA than NuGet :)
This is always an interesting problem to tackle. IMO automatic releases on a push to the default branch are overly chatty. A middle-ground I've used in the past is to cut a new release when a new tag is created.
I wrote this action a couple of years ago to do just that. After a tag is applied, GitHub updates all the relevant bits of the repo to have the correct version from the tag, pushes that to main, and then force pushes the tag to the new hash that it created. After that's done, it builds the project and releases it to NuGet. NOTE: this can be a pretty low priority, even if NuGet releases through the UI can be a manual process, they're really straight-forward to do.
I wrote the parallel action for maven releases: which I found much more valuable because releasing through sonatype is such a bigger PITA than NuGet :)