Our public changelog, and why we keep one

Plenty of dealers have been burned by software. The feature that quietly vanished. The price that changed without an email. The "update" that broke the one screen you used every day, with no word on what happened or when it'd be fixed.

We keep a public changelog so you don't have to guess what changed. Anything a customer would notice goes on it, dated, in plain English.

What's on it

Each card is one day. Under it are the changes that went out that day, each tagged Added, Changed, Fixed, Removed, Deprecated or Security. When a day has a longer write-up, the card links to it here on the blog.

It covers everything we run, not just the website. That includes the backend and the service that syncs distributor feeds, so a fix to how we read a distributor's stock file shows up next to a new button in search.

As of late September 2026 it has 233 releases on it, going back to February.

What a line looks like

The lines are written for dealers, not for us. Take a real sync fix from August. The commit message said "a guard against price-shaped quantities". Written for the changelog, that becomes something like "a distributor's feed sometimes put prices in the quantity column, and we now catch it before it reaches your stock numbers."

We don't list version numbers on the public page. You don't care that it was version 1.103.2. You care what changed and when.

How an entry gets there

Every time we ship, the release starts out as raw commit messages, and none of it is public. Someone then rewrites each line in plain English and marks it as either something a customer would notice or something only we care about. We delete the noise, like dependency updates and formatting changes, outright.

Two things have to be true before anything reaches the public page. A line has to be marked as customer-facing, and the release has to be approved. A release that only had internal changes never shows up. That's the right outcome, since there was nothing for you to notice.

The mobile app waits longer. Its notes stay unpublished until the update is actually in the App Store and Google Play, so we never announce something you can't download yet.

Where we've slipped

This process has failed once already, in the direction of saying too little. In August, four releases sat unpublished for days with finished notes written, because nobody clicked approve. Nothing false went out. Real changes just weren't announced.

Also, the records on the page before August 2026 were backfilled. We moved the changelog to this approval process in August and wrote up the earlier releases after the fact.

What stays off it

Internal changes, like refactors, test fixes and tooling, are written up in plain English too, but they stay off the public page. They're real work, but you wouldn't notice any of it.

Why bother

Because you should be able to check. If a feature you rely on changes, you should be able to find out when and why without opening a support ticket. And if we say something is fixed, there should be a dated line that says so.

The changelog is public and doesn't need an account. Posts like this one are where we explain the bigger changes in more detail.