[question] (pre) releases

Disclaimer: this is probably an information mostly useful for the development team and the contributors.

In #2267 we discussed about the release cycle and how this affects development.
It happens that in those days I'm working hard on integration pipelines and pushing fixes upstream, I do need to have a quick feedback cycle to connect all the dots.

I found out that the `create-release.yml` doesn't exists anymore, so releasing from the fork becomes more tedious than only pushing a tag.
I restored a version of it [here](https://github.com/andreaTP/kiota-prerelease) to be able to self-service releases.

I imagine that this is a pain point also for the internal development team(especially for breaking changes).
Keeping a version of this workflow updated should not be a lot of work and will probably benefit everyone, having to re-create it is more costly.

Thoughts?

Start by reading issue #2267, checking the repository history for the missing create-release.yml workflow, and reviewing the referenced prerelease repository. Clarify with maintainers whether fork-based pre-releases and breaking-change feedback are in scope, then define completion around an agreed, maintainable release workflow.

Written by the indexing model from the issue text.