Find out what a build number contains
The bottom of every Turtini page shows a build number, such as **build 0a11a3b77**. It names the exact code you are running.
**See what a build contains**
1. Select the build number in the footer. The Builds page opens on that build.
2. Choose **Details** to see the features merged in that release, its changes, the areas it touched and the domain services it updated.
3. Choose **Show all builds** to see every recorded release.
**Search and filter**
Type a build number, a feature or an area (for example "Maps") in **Search**. Narrow by **From** and **To** dates, by what was deployed (**Web app**, **Functions** or **Domain services**), or to **Production releases only**. Dates are shown in your own time zone.
**Your build**
The build you are running is marked **Your build**. A release is listed within about a minute of shipping. If the page cannot reach the current list it shows the copy that came with the site, which ends at the release before yours, and says your build is newer than the last recorded release.
**Security fixes**
A release that included security fixes is marked **Security fixes**. What they fixed is not described, so the description cannot help anyone find the same problem elsewhere.
**When reporting a problem**
Include the build number. It tells us exactly what you were running.
**For tools and AI assistants**
The same history is published as JSON at turtini.com/builds/live.json, updated within a minute of each release, and at turtini.com/builds.json, a copy that ships with the site and lists the releases before it. Both are newest first. Each release has its build number (`sha`), other short forms it was recorded under (`aliases`), the full commit, its release time in UTC, what it deployed, a one-line summary, and its features and changes. A build number matches a release when one is the start of the other.