Release Activities

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.

Release Candidate Activities

@definitelytyped/header-parser and retag

Once master's version is updated, the @definitelytyped packages must be aware of the nightly's new version so that functionality such as ATA continues to work.

• Update @definitelytyped/typescript-versions to support the next version, and publish new version
  • in other words, if we're releasing TypeScript 3.9, the header parser needs to support 4.0.
  • To do this, add the new version to the supported list.
• Run @definitelytyped/retag to add the tag ts4.0 to each package.

Release Activities

Release

• Tag release branch
• Update AUTHORS.md for the release (script)
• Draft and publish new release
• Close milestone corresponding to the release

Wiki

• Update What's new in TypeScript
• Update Breaking Changes
• Update API Breaking Changes

Handbook

• Add new Release Notes page for the new release
• Update Handbook (As needed)

npm

• Publish new version of typescript
• Publish new version of tslib (if needed) by creating a tag

Nuget

• Publish new release to https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild/

Visual Studio Marketplace

• Publish VS 2015 and VS 2017 installers under TypeScript team

TypeScript-Sublime-Plugin

• Update version of tsserver, test, and tag

dtslint and types-publisher

After the release version is published to npm:

• Update @definitelytyped/typescript-versions: move the newly published version from supported to shipped (in the example above, that's 3.9), and publish new version of @definitelytyped.
• Update dtslint and dts-critic's dependency to the new @definitelytyped/header-parser
• Update @definitelytyped/publisher's dependency on dtslint. You may still need to clear caches on Travis, although it usually caches npm packages correctly.

Website

• Update Handbook
• Add new release notes page
• Update playground
• Update version strings in the download banner

Additional activities

When a new syntax or a new compiler option is introduced, find below the list of additional release activities needed:

New compiler option added

MSBuild tasks and targets

• Add support for new option in MSBuild tasks and targets (see handbook)

Handbook

• Add new option to Compiler Options
• Add new option to Compiler Options in MSBuild

SchemaStore

• Add new option to tsconfig.json schema
• Add new option to jsconfig.json schema

New syntax introduced

Colorization

• Add colorization support in TypeScript-TmLanguage

Babel

• Add parsing support in Babylon
• Add emit support to babel-plugin-syntax-typescript
• Update the TypeScript-Babel-Starter as needed

Handbook

• Add new section for the new feature in the handbook