-
Notifications
You must be signed in to change notification settings - Fork 12.5k
Release Activities
Nathan Shively-Sanders edited this page Feb 18, 2020
·
29 revisions
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.
Once master
's version is updated, surrounding projects must be aware of the nightlies so that functionality such as ATA continues to work.
- 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 dt-retag to the new header-parser and run it to add the tag for
typescript@next
to each package.
- 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)
- 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
After the release version is published to npm:
- Update dtslint's dependency to the new header-parser
- Update types-publisher's dependency on dtslint. Be sure to clear caches on Travis since it doesn't know how to cache github dependencies correctly.
- Run dt-retag again so that packages published during the RC period get the new version's 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
News
Debugging TypeScript
- Performance
- Performance-Tracing
- Debugging-Language-Service-in-VS-Code
- Getting-logs-from-TS-Server-in-VS-Code
- JavaScript-Language-Service-in-Visual-Studio
- Providing-Visual-Studio-Repro-Steps
Contributing to TypeScript
- Contributing to TypeScript
- TypeScript Design Goals
- Coding Guidelines
- Useful Links for TypeScript Issue Management
- Writing Good Design Proposals
- Compiler Repo Notes
- Deployment
Building Tools for TypeScript
- Architectural Overview
- Using the Compiler API
- Using the Language Service API
- Standalone Server (tsserver)
- TypeScript MSBuild In Depth
- Debugging Language Service in VS Code
- Writing a Language Service Plugin
- Docker Quickstart
FAQs
The Main Repo