Search code, repositories, users, issues, pull requests...

submited by

Style Pass

2024-11-19 11:30:05

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

I guess this can be considered as a bug as it is breaking my apps. If version 2.1.0 has breaking changes, why don't set it to 3.0.0? Semantic versioning, right? Typescript lives and has important role in the nodejs ecosystem, therefore should follow some basic rules. We can not use the npm's semver features to block only major changes.

Expected behavior: Follow semantic versioning rules Actual behavior: Just follows marketing versioning rules can be related to #6520 created a year ago and closed without being solved

TypeScript, however, promises no breaking changes after a stable release. so no breaking changes between 2.1.5 and 2.1.6, 2.1.*.