Release notifications
hho opened this issue · comments
Before, I subscribed to only the releases of this repository – and all was well!
But now I get a release notification for every new commit on master ("Next release development build").
Can I suggest to do the CI for master, but not make a GitHub release?
Hi, sorry for the inconvenience.
This is due to the automation of the release process. It was manual until recently, and very cumbersome.
I've now applied a continuous release process, which occurs at every commit to master using a github action which provides a lot of functionality that was manual beforehand.
This allows a much less error-prone release process, including proper testing of the actual output artifacts by multiple people before making the release official.
The newly "development release" is marked in GitHub as a "pre-release", which is meant for that purpose.
I was under the impression that GitHub does not send notifications/webhooks on pre-releases, although your question proves otherwise.
What kind of integration process do you have with the new releases? Is it just an email, or do you have some programmatic logic running whenever a new release is issued?
looked at it a bit further. Watching only real releases and not pre-released is not yet supported by GitHub and they consider it a bug that will be fixed at some point.
Really sorry for the inconvenience it causes you. However, as this makes the release process much more robust, I currently don't have plans to change it.
OK then 😦