Versions and history
Every build saves a version, and a version's design and fab files never change. You can open, compare, label and fork any of them.
A version is a directory holding the design, the board data, every fab file, the
3D models and a standalone viewer. Versions are numbered v001, v002 and so
on, per project. No action deletes a single version.
Two things add to a version after it is built:
| What | What it writes |
|---|---|
| Simulate, in the chain | sim.json, beside the version's board.json |
soldermask projects rejudge | Runs KiCad's DRC again on the copper. Where the verdict moves, it writes a new board.json and keeps the first as board.json.before-rejudge. |
So a version's verdict can change when it is judged again. The design, the Gerbers and the KiCad files stay as they were.
The version menu
The version chip in the workbench's header opens the version menu. It lists every version, newest first. Each row shows the verdict light, the version, its label, the prompt (or the summary, for an imported version) and the cost. The version on screen is tinted.
Click a row to open that version and make it current. Click its chevron to see:
| Part | Shows |
|---|---|
| The facts line | When it was built, parts, gaps, cost, parent, and the soldermask version that built it |
| The turn | How the verdict changed from the version before, such as GO → NO-GO, and why |
| Summary and notes | The model's summary, and any notes you added |
| The changes | Parts and nets added, removed and changed against the parent, and board name or size changes |
| Files | gerbers.zip, standalone.html, design.json and the KiCad files. More files lists the rest. See Exports and files. |
Under the files are three actions:
| Action | Does |
|---|---|
| Label | Gives it a short name, such as sent to fab or rev B. The label shows on the version chip and on the projects page. |
| Notes | Adds your own notes |
| Fork from here | Starts a new project from this version |
At the foot of the menu, Import a file builds a design.json as the next
version, or reads a .kicad_pcb as one. The whole project goes out from
Export in the header. See Exports and files.
What "current" means
A project has one current version. The workbench opens it by default.
Opening a version from the version menu makes it current. A version opened by
its address, such as a shared link, becomes current when you send a message,
rebuild or route on it. The next edit always builds on the version on screen.
Nothing is lost: the later versions stay in the list. A new edit from an older
version gets the next number, with its parent set to the older one.
The projects page and soldermask projects show both mark the current version.
Diffs
A diff compares two design.json files, not the model's description of what it
did.
- A part counts as changed when its kind, value, package, search term or purpose differs. Its LCSC code is not compared, so a part pinned to another code with the same value and package reads as unchanged.
- A net counts as changed when its set of pins differs.
The reply's changes line is built from the same diff. The API serves it at
/api/projects/<slug>/versions/<vid>/diff?against=<other>.
Where DRC found each problem in a version's copper is
/api/projects/<slug>/versions/<vid>/markers. It reads the markers the build
kept, or asks KiCad's DRC again for a version that kept none, and writes
nothing.
Forks
A fork is a new project whose v001 is a copy of the chosen version. Its
parent records <project>/<version>.
Fork when you want to try a different direction, without its versions mixing with the original's.
On disk
A project is a directory you can read, back up or copy. See Projects on disk.
Chat and decisions
You edit a board by talking to it. Ask a question and get an answer, or ask for a change and review it before it becomes a version.
Exports and files
Every file a fab, an assembler or KiCad needs is saved with the version. You can download one version's files, or the whole project as one zip.