RFE: is it possible to retart making github releases?🤔

[kloczek]

On create github release entry is created email notification to those whom have set in your repo the web UI Watch->Releases.
gh release can contain additional comments (li changelog) or additional assets like release tar balls (by default it contains only assets from git tag) however all those part are not obligatory.
In simplest variant gh release can be empty because subiekt of the sent email contains git tag name.

I'm asking because my automation process uses those email notifications by trying to make preliminary automated upgrades of building packages, which allows saving some time on maintaining packaging procedures.
Probably other people may be interested to be instantly informed about release new version as well.

Documentation and examples of generate gh releases:
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://cli.github.com/manual/gh_release_upload/
jbms/sphinx-immaterial#282
https://github.com/marketplace/actions/github-release
https://pgjones.dev/blog/trusted-plublishing-2023/
jbms/sphinx-immaterial#281 (comment)
tox target to publish on pypi and make gh release https://github.com/jaraco/skeleton/blob/928e9a86d61d3a660948bcba7689f90216cc8243/tox.ini#L42-L58

[bgoglin]

Are you talking about (1) releases that github automatically builds when we push a tag? Or about (2) us storing our official release tarballs in GH releases?
I don't like (1) because GH doesn't really "builds" release, it just jacks the repository but it doesn't run autogen, doesn't generate the documentation, etc.
(2) is done manually but I always forget to do it.

[kloczek]

No I'm talking about only add githib release which adds entry on https://github.com/open-mpi/hwloc/releases and causes sending email notifications.

[kloczek]

(2) is done manually but I always forget to do it.

In links which I've provided are details about how to automate that 😋

[bgoglin]

By the way, when did you stop getting email for releases? I changed one thing in the config of github 1 or 2 weeks ago so that the release info doesn't appear anymore on the right, but I don't think it disabled the building of those GH releases when tagging (but I haven't pushed any tag since then). Before that, I manually uploaded our release tarballs to GH a couple times, but it looks like this was really only a couple times several years ago (2.1.0 and 2.0.2), hence I am surprised you had time to build a workflow on top of this.

[kloczek]

Please .. creating githib releases have nothing to to with building anything.

Receive email notifications is controlled over Watch->Releases.

[bgoglin]

Citing your first post "my automation process uses those email notifications by trying to make preliminary automated upgrades of building packages"

[kloczek]

Yes it uses .. but it is not only about my automation. It is about all those who have set Watch->Releases.

[bgoglin]

I just published a release for 2.10.0 as I did in the past (add our official tarballs to the dumb GH release with a big message saying that's not the official release page), see https://github.com/open-mpi/hwloc/releases/tag/hwloc-2.10.0
Does this help? I don't have time to investigate much more than this.

[kloczek]

Thank you 👍

[bgoglin]

Ok, if this looks good, I will try to make that for non-RC releases.

[kloczek]

Thank you very much 👍 😄