Skip to content

Release Activities

Gabriela Araujo Britto edited this page Aug 22, 2024 · 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.

The primary people managing a release should oversee these tasks along with the overall release process.

Release Candidate Activities

tslib

  • Add all tslib updates
  • Review next version number

@definitelytyped/typescript-versions and @definitelytyped/typescript-packages

Once main's version is updated, the @definitelytyped packages must be aware of the nightly's new version so that nightly versions of ATA continue to work. ATA relies on tsX.Y tags on @types/* packages.

Release Activities

Release

  • Tag release branch
  • Draft and publish new release
  • Close milestone corresponding to the release

Project Health

Wiki

Handbook

npm

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

Nuget

Visual Studio Marketplace

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 a new release of @definitelytyped.

Website

  • Update Handbook
  • Add new release notes page

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)

New syntax introduced

Colorization

Babel

Handbook

  • Add new section for the new feature in the handbook
Clone this wiki locally