Versions and releases
Every change to a table makes a new version. A checkpoint names a version so you can come back to it, and a release is the version everyone outside your model reads, so you can keep working while their numbers stay put.
Three ideas
| What it is | Who reads it | |
|---|---|---|
| Latest | The table as it is now | People who can edit the model, as they work |
| Checkpoint | A version you named, kept for good | Anyone restoring or comparing |
| Release | The checkpoint you publish | Importers, people you share the table with, AI assistants without edit rights, and datasets |
A new version is made by every change to the data or the columns: an edit, a commit, a sync, a column added or retyped, a unit set. Moving or resizing a table on the canvas changes no data, so it makes no version.
Open the history
Select a table and click Checkpoints on the action bar, or open the Checkpoints section in the details pane. The panel lists the table's checkpoints and releases, newest first.
- Find a checkpoint searches by name or alias.
- The All / Releases filter narrows the list to releases.
- The panel's head shows where the latest version stands, and offers New checkpoint and New release when it isn't saved yet.
Checkpoints
A checkpoint keeps one version so you can restore it, compare it or release it later. Take one before any change you might want to undo as a whole: a big paste, a Search & replace in place, a sync from a source you don't control.
To make one, click New checkpoint in the panel and give it a name. Anyone who can edit the table can make checkpoints.
Checkpoints are what Mycorr keeps for good. The latest version, every checkpoint and every release are always kept. Older versions that no checkpoint names may be cleaned up over time, so checkpoint anything you want to be able to return to.
Names and aliases
Each version can have one checkpoint, and a checkpoint can carry several names, called aliases. Renaming a checkpoint adds the new name as an alias; Make default chooses which one shows. Find a checkpoint matches any of them.
What you can do with a checkpoint
From a checkpoint's menu:
- View the table at this point opens the table as it was.
- Restore brings the table back to that state. The restore is itself a new version, so nothing in between is lost and you can restore forward again.
- Release checkpoint publishes it as the table's release.
- Rename or Delete it.
Compare two versions
- Click Compare two checkpoints in the panel.
- Pick the two points to compare. The latest version needs saving as a checkpoint first.
- Click Compute diff.
The diff lists the Added rows, the Removed rows, and the Edited cells, old → new. An edit made in Mycorr shows as edited cells. Only a connected table synced with No primary key shows an edited row as one row removed and one added, because its rows are matched by their content.
Releases
A release is the version of a table that people outside its model get. When you share a table or someone imports it into another model, they read the release, never your work in progress. A half-finished change never reaches anyone until you release it.
- Set as release on the action bar releases the current version. In the panel, New release does the same.
- Release checkpoint releases an older checkpoint instead.
- A table has one release at a time. Releasing again replaces it; earlier releases stay in the history, marked Released with their date.
- Unrelease takes the release away. It is refused while other models import the table (release another checkpoint instead) or while the public catalog serves the release.
In the details pane, the release figure in the table's header shows which version is released. Hover it and click Compare released with current to see what has changed since.
Anyone who can edit the table can release it. Tables in a public catalog dataset are released through their dataset instead.
Sharing a table needs a release. If a table has none, the share dialog offers Add a release first. See Share a table.
Imported tables
When you import a table into your model, your model reads the release it was given and stays on it. New edits in the original never change your numbers behind your back.
- The history panel is titled Releases and lists the owner's releases. In use marks the one your model reads.
- When the owner releases a newer version, Sync to latest release appears on the table's action bar. Anyone who can edit your model can take it, when they're ready.
- You can't edit an imported table or make its checkpoints; its history belongs to its owner. You can Check out another of its releases from the panel, to read an earlier one.
Tables from a connection
A table synced from a connection has versions like any other: every sync that changes something makes one, and Checkpoint, then sync saves a checkpoint first so you can go back if the new data is wrong.
Its history panel also shows the table's Primary key: how rows are matched from one sync to the next. See Row tracking. Restoring a checkpoint taken under a different key asks which key the restored table should use.
AI assistants
The same rule holds through the MCP server: an assistant that can edit a table reads its latest version, and any other reads its release. A table with no release can be read only by people who can open its model.