Configure pre-releases as draft to avoid unnecessary notifications

[SimonMarquis]

The current GitHub workflow development-release.yml overwrites any current GitHub pre-release on every commit, which is advertised by email/notification while this is actually not really a pre-release per say. Would you be open to test making it a draft pre-release to see if it prevents the notifications for each commit on the main branch?

This would allow us to actually be able to follow "real" releases, and not be notified for each commit.
I'm not sure if this will work, but it is worth a try.
Thanks

[erichaagdev]

Hi, @SimonMarquis! Thank you for the issue and PR. We will discuss this internally.

[erichaagdev]

Hi, @SimonMarquis. We've decided the best way to handle this is to remove automated development releases on merges to main. We had originally done it that way for testing purposes, but we feel it's no longer necessary and can instead build from source and test.

We still find having development releases useful so we will keep them around, but they will be created manually on an as needed basis, which I estimate to happen very infrequently.

We will take care of implementing the necessary changes, so you can close your PR. Thank you very much for your contributions!