Changelog & roadmap
These documentation pages describe exactly one thing: Tinspec v0.1.0-preview.9, released 2026-09-09. 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 |
| Pricing and the cloud tier | tinspec.dev/pricing |
| Support | tinspec.dev/support |
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.
- The CLI runner — the engine is headless specifically so one can exist. It does not ship yet.
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.