We’re Switching to Calendar Versioning: Here’s Why – Source: securityboulevard.com

Calendar Versioning is a system where version numbers are tied directly to the release date. Our new format is:

..

For example, version 2025.5.1703 corresponds to a build released in May 2025, with 1703 being our internal build identifier.

Unlike semantic versioning (SemVer), which emphasizes the types of changes (breaking, minor, patch), CalVer shifts the focus to when a release was made. That’s a subtle but powerful change.

Why we’re making this change

As a security-focused company, our software lifecycle is rooted in continual improvement. We release frequent updates (patches, enhancements, and performance optimizations), often in response to real-world feedback or evolving threat models.

SemVer forced us to shoehorn meaningful updates into an artificial scheme. What’s a patch? What’s a minor? What’s a breaking change when your whole mission is zero-friction upgrades?

With CalVer, we’re embracing what we already do:

• Frequent releases that improve security and stability.
• Predictable versioning that customers and integrators can align with.
• Simple traceability, if you see 2025.5, you know precisely when it shipped.

What this means for you

If you’re a customer:

• Your upgrade path will not be affected. You will still receive updates through the same channels you use today.
• Version clarity improves. You can now understand recency at a glance, so there is no need to dig into changelogs or support docs to interpret v0.111.0 vs v0.106.1

Why now?

Frankly, it was overdue.

We’ve grown rapidly in both deployment scale and update frequency. Our original versioning scheme served us well during our early days, but it started to become more of a constraint than a compass. Calendar Versioning brings us back in sync with our development and deployment rhythms.

Looking ahead

We’ll continue to ship on a regular cadence. You’ll always know when a release is dropped, and we’ll continue publishing changelogs with the same transparency you expect.

As always, we welcome feedback – especially from teams that’ve already adopted CalVer or are considering it. We’d love to chat if you’re curious, skeptical, or just excited about this kind of operational detail.

Onward.

Granville Schmidt
Chief Architect