TableCore

Updates

How they are delivered

Windows builds update through Velopack on the win-x64-stable channel. Versions are Year.Feature.Fix, so 2026.1.0 is the first feature release of 2026 and 2026.1.1 is a fix on top of it.

The update feed is the only place TableCore looks:

https://releases.tablecore.dev/updates/win-x64-stable

That host serves the private release storage through a gateway. There is no mirror and no alternative channel.

When it checks

Once, when the window opens. After that, only when you ask.

If a newer build exists it downloads in the background, and the title bar tells you when it is ready. Applying it is your decision — nothing restarts on its own.

Help → Check for updates asks again at any time.

The two paths differ in how loud a failure is allowed to be:

CheckOn failure
The one at startupSays nothing. You did not ask, and there is nothing you can act on
Check for updatesReports the failure. You are waiting for an answer

A download in flight and a ready update are always shown, because a multi-megabyte download on somebody's connection is not allowed to be silent.

Your open tabs survive it

Applying an update is not a window close: Velopack hands over to the updater and the process goes, so the handler that normally saves your session on exit never runs. TableCore therefore writes the session to disk before handing over. Without that, "your tabs come back" would be true only of whatever the autosave had already written — and the sentence you were typing when you pressed the button would be the one thing the update lost.

When there is no update path

A build you compiled yourself does not update

The update interface exists only for a copy installed by the Velopack installer. A development build run from source has no feed to ask, so the interface is absent rather than present and failing.

macOS and Linux have no published builds, so they have no update channel either. See Installation.

When an update fails

  1. Check the feed is reachable. A corporate proxy or a firewall blocking releases.tablecore.dev is the common cause.
  2. Try again from Help → Check for updates. That path reports the actual error rather than staying quiet.
  3. Install over the top. Download the current Setup.exe from the download page and run it. Your data directory and your credential store entries are untouched by a reinstall, so your connections, workspace and history come through.
  4. Verify the download against its SHA-256 checksum from the release archive if the failure looked like a corrupt package.

Remember that installers are unsigned, so Windows SmartScreen will warn you again. That is expected — see Installation.

Going back to an older build

Older builds stay in the release archive with their sizes and checksums. Installing one over a newer one is a downgrade Velopack does not manage for you; treat it as a fresh install of that version.

Note that the channel manifest is only published after the artifacts have been uploaded and checksum-verified, so a version that appears in the feed is one that has been verified as downloadable.