binance
Question: about updates and versions of updates
Hello,
Could you clarify what versioning system you use to determine update releases? I’ve noticed that the recent versions (e.g. 13.0.0 → 15.0.0 → 16.0.0) don’t seem to introduce full major changes. Instead, they include mostly minor additions or removals, with only partially breaking changes to previous code.
Since I carefully track each release, I end up reviewing the entire changelog, even when the updates don’t affect my code because there are no truly critical changes.
Understanding the versioning strategy would help me (and likely others) better assess the impact of updates without having to re-read everything unnecessarily.
Thank you!
Hi @Galllarate,
Thanks for raising this — great question.
The short answer is that we use Semantic Versioning following community standards (Patch = fixes, Minor = backward-compatible additions, Major = anything that could break some usage). Because the SDK surface is large and partly produced by automated tooling, we mark subtle type/behaviour changes as major to avoid silent breaks (similar to other large SDKs).
You can check each release’s Breaking changes section; if nothing affects you, it’s safe to upgrade. We never ship breaking changes in minors/patches.
