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

El issue no identifica ningún archivo del repositorio, workflow, prueba ni punto de entrada que deba modificarse. Empieza revisando el proceso existente de release y publicación en PyPI, y después compáralo con el objetivo de publicación de tox enlazado y la documentación de releases de GitHub. El trabajo debería considerarse terminado cuando incluya un workflow de release acordado que cree el release de GitHub previsto y conserve el comportamiento existente de publicación de paquetes.

Escrito por el modelo de indexación a partir del texto del issue.