Changelog & roadmap
These documentation pages describe exactly one thing: Tinspec v0.1.0-preview.10, released 2026-09-13. Release history and future plans live on the marketing site.
| What | Where |
|---|---|
| Release notes for every version | tinspec.dev/changelog |
| Planned and in-progress work | tinspec.dev/roadmap |
| Downloads, checksums, install notes | tinspec.dev/download |
| The CLI runner, which versions separately | tinspec.dev/download#cli |
| Pricing and the cloud tier | tinspec.dev/pricing |
| Support | tinspec.dev/support |
Two version lines
Section titled “Two version lines”The desktop app and the headless runner ship independently, so these docs name two versions and they will not stay in step:
- The app —
v0.1.0-preview.10, which is what the badge in the header states and what every page here was verified against. - The CLI —
tinspecv0.1.1, covered by Run a suite in CI and the CLI reference. It is built on the same engine release the app embeds, which is the only reason the two can be documented as behaving identically.
This app release shipped a macOS build only. There is no preview.10 Linux or Windows file, and no promise here about when there will be — an existing install on either keeps working and simply is not offered this update. See Install and the download page for what is actually downloadable today.
Why the separation
Section titled “Why the separation”Documentation that mixes “this is how it works” with “this is how it will work” stops being usable, because the reader can no longer tell which sentence they can act on.
So the rule here is absolute: nothing is documented unless it is in a downloadable release. If a capability was uncertain at verification time, it was left out rather than guessed at. An absent page costs you a search; a wrong one costs an afternoon.
The version badge in the header states which release these pages describe, and it links to the changelog.
Deliberately not documented yet
Section titled “Deliberately not documented yet”Real features whose pages are waiting on something:
- Cloud sync and tunnels — the desktop half ships in this release, but the hosted service is not open for sign-up, so no walkthrough could be completed. See Local & cloud.
That list used to carry the CLI runner, described as an engine capability with no program behind it. There is a program now, and it has its own two pages.
When a new version ships
Section titled “When a new version ships”These docs are re-verified against the new tag before anything new is claimed, and the version badge moves. Where a prior version needs to stay readable, it is snapshotted into its own section rather than edited in place — so a link to something you read last month keeps describing the build you were running.