microsoft
TypeScript 5.8 Iteration Plan
This document outlines our focused tasks for TypeScript 5.8. It minimally indicates intent to investigate tasks or contribute to an implementation. Nothing is set in stone, but we will strive to complete these tasks in a reasonable timeframe.
| Date | Event |
|---|---|
| 2024-11-22 | TypeScript 5.7 Release |
| 2025-01-24 | Create 5.8 Beta (5.8.0) Build for Testing |
| 2025-01-28 | TypeScript 5.8 Beta Release |
| 2025-02-07 | Create 5.8 RC (5.8.1) Build for Testing |
| 2025-02-11 | TypeScript 5.8 RC Release |
| 2025-02-21 | Create 5.8 Final (5.8.2) Build for Testing |
| 2025-02-25 | TypeScript 5.8 Final Release 🚀 |
gantt
dateFormat YYYY-MM-DD
TypeScript 5.7 Stabilization Period : 2024-11-18, 2024-11-22
TypeScript 5.8 Beta Development : 2024-11-18, 2025-01-24
TypeScript 5.8 RC Development : 2025-01-25, 2025-02-07
TypeScript 5.8 Stabilization Period : 2025-02-08, 2025-06-21
todayMarker stroke-width:5px,stroke:#0f0,opacity:0.5
Compiler and Language
- Checked Return Statements for Conditional and Indexed Access Types
--module node18and--module node20--erasableSyntaxOnlyOption- Investigate Preserving Computed Properties with Entity Names for Declaration Emit
- Introduce
--libReplacement lib.d.tsUpdates
Editor and Language Service
Performance
Website and Docs
Starting jobs; this comment will be updated as builds start and complete.
| Command | Status | Results |
|---|---|---|
create release-5.8 |
✅ Started | ✅ Results |
Hey, @RyanCavanaugh! I've created release-5.8 with version 5.8.0-beta for you.
Starting jobs; this comment will be updated as builds start and complete.
| Command | Status | Results |
|---|---|---|
sync release-5.8 |
✅ Started | ✅ Results |
Starting jobs; this comment will be updated as builds start and complete.
| Command | Status | Results |
|---|---|---|
sync release-5.8 |
✅ Started | ✅ Results |
Starting jobs; this comment will be updated as builds start and complete.
| Command | Status | Results |
|---|---|---|
bump release-5.8 |
✅ Started | ✅ Results |
Hey, @DanielRosenwasser! I've set the version of release-5.8 to 5.8.1-rc for you.
Starting jobs; this comment will be updated as builds start and complete.
| Command | Status | Results |
|---|---|---|
bump release-5.8 |
✅ Started | ✅ Results |
Hey, @DanielRosenwasser! I've set the version of release-5.8 to 5.8.2 for you.
I don't see the version in rpm registry?
Looks like 5.8.2 was published to NPM shortly after this comment was posted.
https://www.nuget.org/packages/Microsoft.TypeScript.MSBuild has 5.8.1 as latest version which really includes js with this content in it:
var versionMajorMinor = "5.8";
var version = "5.8.1-rc";
Two full weeks later. When can we expect a stable release for 5.8.x via nuget.org ?
cc @DanielRosenwasser
Starting jobs; this comment will be updated as builds start and complete.
| Command | Status | Results |
|---|---|---|
bump release-5.8 |
✅ Started | ✅ Results |
Hey, @DanielRosenwasser! I've set the version of release-5.8 to 5.8.3 for you.
@DanielRosenwasser did you intend to publish the production 5.8.3 release? It is unclear because there is no 5.8.3 Git tag in the repository for the release. This makes it difficult for maintainers of dependent projects to effectively review the changeset that would be introduced by bumping our typescript package dependency.
Please configure your automated release system to also push a Git tag to the repository: https://github.com/microsoft/TypeScript/issues/51553
There is a release in draft form; it is automatically created but requires a manual step as there are more places we need to publish the release than just npm.
GitHub releases and Git tags are two separate things. You can push a Git tag via the automated release system, then later create a GitHub release for that Git tag.
I very much understand that. Our publisher very intentionally does not have permission to push tags (or anything else) to the repo.
Please be patient. We'll create the tag soon.
Our publisher very intentionally does not have permission to push tags (or anything else) to the repo.
Fine, then you should instead change the procedure followed by the human who performs the release to include the pushing of a tag.
We'll create the tag soon.
Thanks. I do appreciate that, but am more interested in the system or procedures being improved so that this situation doesn't continue to occur
@RyanCavanaugh the thumbs downs on my comments seem a bit petty. Was there something technically inaccurate in what I wrote? Or are you just offended by me pointing out a pattern of failure to follow basic project maintenance best practices by the maintainers of one of the world's most significant software projects?
@per1234 no offense taken, you're just being a bit abrasive about this. Our release process is subject to security constraints you may not be aware of, and we'd ask that you adopt a friendlier tone instead of using every available opportunity to speak negatively about the project and the people working on it. 99% of people operating here don't need to use this kind of tone when discussing routine operations.
Take your own advice. It was you who introduced negativity with arbitrary thumbs downs.