Hello Everyone,
We’ll be moving all of Speckle’s products to a calendar-based versioning scheme.
The primary goal is to make it easier to understand the compatibility status of releases across our platform.
Future releases will follow the versioning format:
Year.Month.Patch
For example, 2026.6.0 would be the first release published in June 2026.
Additional releases during that month would increment the patch number.
Any products with the same Year and Month will have full compatibility.
We’re not changing our release cadence, or backwards compatibility commitments, or the way we give notice of API deprecations. This change only affects how versions are numbered, and will affect Speckle’s Connectors, Server, SDKs, Viewer, and certain internal systems.
What’s wrong with the current versioning system?
Speckle’s products all have different release cadences, are built on different technologies, and by different sub-teams inside Speckle, and so end up with different version numbers.
For example; server version 3.0.40, python SDK 3.2.8, and Sharp Connectors 3.24.1. It’s not obvious that these were all compatible versions released around the same time.
We hope that switching to calendar versioning will be a positive change, brining clarity.
If you have any questions, please don’t hesitate to drop them below.