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

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://github.com/getmoto/py-partiql-parser/commit/a58a3783
https://docs.github.com/en/repositories/releasing-projects-on-github/managing-releases-in-a-repository
https://cli.github.com/manual/gh_release_upload/
https://github.com/jbms/sphinx-immaterial/pull/282
https://github.com/marketplace/actions/github-release
https://pgjones.dev/blog/trusted-plublishing-2023/
https://github.com/jbms/sphinx-immaterial/issues/281#issuecomment-1700933026
tox target to publish on pypi and make gh release https://github.com/jaraco/skeleton/blob/928e9a86d61d3a660948bcba7689f90216cc8243/tox.ini#L42-L58

L’issue n’identifie aucun fichier du dépôt, workflow, test ou point d’entrée à modifier. Commencez par examiner le processus existant de release et de publication sur PyPI, puis comparez-le avec la cible de publication tox liée et la documentation des releases GitHub. La définition de terminé devrait inclure un workflow de release convenu qui crée la release GitHub prévue et préserve le comportement existant de publication des paquets.

Rédigé par le modèle d'indexation à partir du texte de l'issue.