Version Management
The Releases page shows every published version of your project. Open it from the version number in the app header.
It appears once you've published at least one version, on plans that include version history.
What's in the table
Each row is one release:
| Column | What it shows |
|---|---|
| Version | The version number like v0.1.0. The most recent one has a latest badge. |
| Released | When it was published |
| Changes | A quick summary, like "22 tokens added" |
| Release Notes | Whatever was written at publish time |
| Download | Download the token file for that version |
| Copy | Copy the token data to your clipboard |
Getting a specific version
Click Download on any row to get the token file for that release. Useful when a developer needs to pin to a known version, or when you need to get back to a set of values that worked. A developer can also set that version in bezel.json version and the MCP server pulls it for them.
The Copy button puts the token data on your clipboard, which is handy for pasting into a config file or sharing directly.
The latest badge
The row marked latest is the most recently published version. Older versions stay accessible, so you can always retrieve one.
Releases are downloadable snapshots, not a version-control system. Getting back to an older set of values means downloading that version and importing or committing it yourself. Bezel won't roll the project back for you.
Why bother with versions
Each release is a stable snapshot. If something breaks after a later change, you can scroll the history, find the last version that was working, and pull it. Good release notes make that much faster. It sounds like overhead until the first time you need it.