Comment by colinmarc
2 days ago
It's conventional for semver to allow breaking changes for 0.x minor releases (but not for patch releases).
2 days ago
It's conventional for semver to allow breaking changes for 0.x minor releases (but not for patch releases).
Yes but the question is why Ruff has not released v1 yet. They’re clearly used in production and the entire purpose of v0.x is to signal a project is early in development and is expected to have coarse edges.
The versioning doc linked elsewhere in the thread explains: There isn't yet a stable API and they want to wait on that before releasing v1.