Start following semantic versioning

该 issue 没有指定任何文件、测试或入口点。请先阅读现有讨论以及项目的 release/versioning 流程；要完成这项工作，需要先就采用 Semantic Versioning 达成一致的计划，而不是进行局部代码更改。

🔍 Search Terms

semantic versioning

✅ Viability Checklist

• This wouldn't be a breaking change in existing TypeScript/JavaScript code
• This wouldn't change the runtime behavior of existing JavaScript code
• This could be implemented without emitting different JS based on the types of the expressions
• This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
• This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
• This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

⭐ Suggestion

Start following semantic versioning from now on.

I know TypeScript currently doesn't follow semantic versining, and push breaking changes for every minor version. I could not find any mention as to why it is the case.

There is no reason TypeScript cannot follow semantic versioning. There is simply no other major library that doesn't follow semantic versioning in NPM ecosystem. There is also no problem with pushing major version every other months. It just means the version will be incrementing a lot quicker. It means it follows the ecosystem's standard and more predictable for a lot of people.

📃 Motivating Example

• Version update is more predictable and follows standard of the Node.js/npm ecosystem.
• You no longer have to change ^x.y.z to ~x.y.z every time you run npm i -D typescript

💻 Use Cases

1. What do you want to use this for?
   • More predictable and standard versioning when installing TypeScript
2. What shortcomings exist with current approaches?
   • Non-standard versioning in the ecosystem
3. What workarounds are you using in the meantime?
   • Change ^ to ~ in the version specifier