CI Automating of Releases

[JamieDanielson]

Tracking issue for the rest of the items we are automating in releases based on comment in #4849 :

Still missing:

• automatically determining which release scope and type is required
• actually releasing the packages once the PR is merged (currently needs to be done manually via NODE_AUTH_TOKEN=<your-token-here> npm run release:publish)
• automatically creating the releases once the PR is merged (currently needs to be done by running npm run _github:draft_release:stable, _github:draft_release:experimental, _github:draft_release:api) and then publishing the created draft release

[github-actions]

This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 14 days.

[github-actions]

This issue was closed because it has been stale for 14 days with no activity.

[JamieDanielson]

@pichlermarc are we good with the changes that have been made so far or should I reopen this for tracking more updates?

[pichlermarc]

@JamieDanielson I'm good with the current state, they already cut down the complexity to release significantly. 🙂
I'd say we create a new issue if we see room for improvement somewhere.