You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
Daniel Rosenwasser (@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: #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.
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
Ryan Cavanaugh (@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?
Per Tillisch (@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.
Reacted by Alexander Kachkaev, snarbles2, ✦ Cherry Pie ✦, Alvis Tang and Alex Rao
After six weeks we still have no stable release of 5.8 on nuget.org.
If you are dropping nuget support that would be a huge break.
cc Joaquin Jares (@joj)
Activity
RyanCavanaugh commentedon Jan 24, 2025
TypeScript Bot (@typescript-bot) create release-5.8
typescript-bot commentedon Jan 24, 2025
Starting jobs; this comment will be updated as builds start and complete.
create release-5.8typescript-bot commentedon Jan 24, 2025
Hey, Ryan Cavanaugh (@RyanCavanaugh)! I've created release-5.8 with version 5.8.0-beta for you.
DanielRosenwasser commentedon Jan 29, 2025
FWIW we'll probably go out with the beta tomorrow morning.
DanielRosenwasser commentedon Feb 10, 2025
TypeScript Bot (@typescript-bot) sync release-5.8
typescript-bot commentedon Feb 10, 2025
Starting jobs; this comment will be updated as builds start and complete.
sync release-5.8typescript-bot commentedon Feb 10, 2025
Hey, Daniel Rosenwasser (@DanielRosenwasser)! I've pulled main into release-5.8 for you.
DanielRosenwasser commentedon Feb 10, 2025
TypeScript Bot (@typescript-bot) sync release-5.8
typescript-bot commentedon Feb 10, 2025
Starting jobs; this comment will be updated as builds start and complete.
sync release-5.8typescript-bot commentedon Feb 10, 2025
Hey, Daniel Rosenwasser (@DanielRosenwasser)! I've pulled main into release-5.8 for you.
DanielRosenwasser commentedon Feb 12, 2025
TypeScript Bot (@typescript-bot) bump release-5.8
typescript-bot commentedon Feb 12, 2025
Starting jobs; this comment will be updated as builds start and complete.
bump release-5.8typescript-bot commentedon Feb 12, 2025
Hey, Daniel Rosenwasser (@DanielRosenwasser)! I've set the version of release-5.8 to 5.8.1-rc for you.
8 remaining items
typescript-bot commentedon Apr 2, 2025
Starting jobs; this comment will be updated as builds start and complete.
bump release-5.8typescript-bot commentedon Apr 2, 2025
Hey, Daniel Rosenwasser (@DanielRosenwasser)! I've set the version of release-5.8 to 5.8.3 for you.
per1234 commentedon Apr 7, 2025
Daniel Rosenwasser (@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
typescriptpackage dependency.Please configure your automated release system to also push a Git tag to the repository: #51553
jakebailey commentedon Apr 7, 2025
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.
per1234 commentedon Apr 7, 2025
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.
jakebailey commentedon Apr 7, 2025
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.
per1234 commentedon Apr 10, 2025
Fine, then you should instead change the procedure followed by the human who performs the release to include the pushing of a tag.
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
Ryan Cavanaugh (@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?
RyanCavanaugh commentedon Apr 10, 2025
Per Tillisch (@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.
per1234 commentedon Apr 10, 2025
Take your own advice. It was you who introduced negativity with arbitrary thumbs downs.
HolgerJeromin commentedon Apr 11, 2025
After six weeks we still have no stable release of 5.8 on nuget.org.
If you are dropping nuget support that would be a huge break.
cc Joaquin Jares (@joj)
HolgerJeromin commentedon Apr 24, 2025
Yeah, thanks a lot for the missing nuget updates!
5.8.3 5 hours ago
5.8.2 2 days ago
predragnikolic commentedon Jul 24, 2025
Hello 👋
any news regarding "Investigate LSP Support"?
Typescript 5.7 was the last iteration plan to mention it. How did the investigation go?
Any plans to revisit LSP support in a later iteration plan?
jakebailey commentedon Jul 24, 2025
We're working on LSP in https://github.com/microsoft/typescript-go.
See also #39459 (comment)