Releases
Versioning strategy for packages
TypeSpec is currently in its development phase, and all packages are released with a 0. major version. Each minor version may introduce some breaking changes to the TypeSpec language, library API, or both. These changes are documented here.
Any modification to the main branch is automatically published under the npm @next tag.
Available packages
| Name | Changelog | Latest | Next |
|---|---|---|---|
| Core functionality | |||
| @typespec/compiler | Changelog |  |  |
| TypeSpec Libraries | |||
| @typespec/rest | Changelog |  |  |
| @typespec/openapi | Changelog |  |  |
| @typespec/openapi3 | Changelog |  |  |
| @typespec/versioning | Changelog |  |  |
| TypeSpec Tools | |||
| @typespec/prettier-plugin-typespec | Changelog |  |  |
| typespec-vs | Changelog |  |  |
| typespec-vscode | Changelog |  |  |
| tmlanguage-generator | Changelog |  |  |
Release cadence
We roll out updates for all packages during the first week of each month.
To preview upcoming changes, you can check the milestones at https://github.com/microsoft/typespec/milestones. Milestones are labeled according to the target release month.
Breaking changes migration guides
Release notes describing the breaking changes and how to migrate can be found in this folder:
https://github.com/microsoft/typespec/tree/main/docs/release-notes