This is the list of release activities needed for every TypeScript release. Additional activities are also needed if a new syntax is introduced or a new compiler option gets added.
- Tag release branch
- Update AUTHORS.md for the release (script)
- Draft and publish new release
- Close milestone corresponding to the release
- Update What's new in TypeScript
- Update Breaking Changes
- Update API Breaking Changes
- Add new Release Notes page for the new release
- Update Handbook (As needed)
- Update definitelytyped-header-parser to understand the next version, and publish new version
- in other words, if we're releasing TypeScript 3.2, the header parser needs to be able to parse
3.3.
- in other words, if we're releasing TypeScript 3.2, the header parser needs to be able to parse
- Update types-publisher dependency to the new header-parser
- Run the tagging script to tag for new version (version of
typescript@next)
- Publish new version of typescript
- Publish new version of tslib (if needed)
- Publish new release to https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild/
- Publish VS 2015 and VS 2017 installers under TypeScript team
- Update version of tsserver, test, and tag
- Update Handbook
- Add new release notes page
- Update playground
- Update version strings in the download banner
When a new syntax or a new compiler option is introduced, find below the list of additional release activities needed:
- Add support for new option in MSBuild tasks and targets (see handbook)
- Add new option to Compiler Options
- Add new option to Compiler Options in MSBuild
- Add new option to tsconfig.json schema
- Add new option to jsconfig.json schema
- Add colorization support in TypeScript-TmLanguage
- Add parsing support in Babylon
- Add emit support to babel-plugin-syntax-typescript
- Update the TypeScript-Babel-Starter as needed
- Add new section for the new feature in the handbook