Versions & Releases
Two ways to get your tokens out of Bezel: download or publish.
Download
The download icon in the app header exports your current project state as a design-tokens.json file, right now. No version is created, no history saved. It's whatever your tokens look like at this moment.
Good for quickly sharing with someone, testing in a local build, or grabbing a working copy without ceremony.
Publish a release
Publishing creates a versioned snapshot with a number like v0.1.0 and optional release notes. Every release is stored in your project history, so anyone with access can come back later, see what changed, and download that exact version.
Good for developer handoffs that need a stable reference, and for marking milestones. A repo can pin a release by setting its version in bezel.json version, so the MCP server syncs exactly that release.
Publishing requires Foundation or higher. Without it, the publish button and version link don't appear in the header.
Three different meanings of "publish"
The word gets used three ways in Bezel, and they're unrelated:
| What it does | |
|---|---|
| Publish (this section) | Creates a versioned snapshot of your tokens inside Bezel |
| Publish to Figma | Pushes tokens into a Figma file as variables. See Figma |
| Your linked GitHub repo | Nothing. Bezel has read-only access and never writes to it. See Code |
Where to go next
- Creating a Release — the publish flow, step by step
- Version Management — viewing and downloading past releases