Improve release workflow: Generate release notes as an automatic workflow step #131
Description
As part of research from #107 we are reducing the manual steps in our release workflow.
Our current release workflow is documented here: https://github.com/github/workflow-development/blob/main/docs/vscode/release-new-version.md
Our current ideal scenario for release is:
- Go to Language Services and select "major" or "minor" or "patch" and it will pull in the previous version and increment for you based on your selection. A PR will be opened, you approve it and the release is completed. The release and release notes will be autogenerated.
- Go to the VS Code repo and select "major" or "minor" or "patch" and it will pull in the previous version and increment for you based on your selection. You will also be asked "true/false" to pull in Language Services or not. This workflow will automatically create a release PR, incrementing the VS Code and Language Services version by running the NPM steps as a script (if true was selected to pull in Language Services).
This issue is 1 part of 4 for the release improvement.
- Improve release workflow: Setup ability to release individual packages of Language Service #132
- Improve release workflow: Generate release notes as an automatic workflow step #131
- Improve release workflow: Auto-increment version for both VS Code and Language Services based on input of "major" or "minor" or "patch" release #130
- Improve release workflow: true/false input for VS Code release to pull in Language Services + make all local NPM steps into reusable script/steps #129
Tasks for this issue:
- Generate release notes automatically using a script or API call if possible
- Update documentation with all changes https://github.com/github/workflow-development/blob/main/docs/vscode/release-new-version.md