What to Know Before Using GoldenCheetah Snapshot Builds

Updated

GoldenCheetah snapshot builds are pre-release versions published automatically when significant new enhancements are available or when a major bug is squashed. They differ from the stable release (currently version 3.8) in one critical way: they have only been tested by developers, so regressions are possible. If you want to try new features early, snapshots are the way to get them — but you should always take a backup before running one, and you should not rely on a snapshot as your only copy of training data.

How snapshot builds differ from stable releases

Stable release (3.8) Snapshot build
Trigger for publication Official release cycle Significant new enhancement or major bug fix
Testing Released as current stable Tested only by developers
Risk of regressions Lower Possible — "don't be surprised if things go wrong"
Recommended use Everyday analysis Testing new features, with backups

The GoldenCheetah project states plainly that snapshot builds "may contain regressions as they will only have been tested by developers." That is the trade-off: you get fixes and features sooner, but you accept a higher chance of breakage.

Before you run a snapshot build

  1. Back up your data. The project's own guidance is unambiguous: "ALWAYS TAKE A BACKUP BEFORE RUNNING SNAPSHOT BUILDS." Export or copy your athlete data and configuration so you can restore it if the build misbehaves.
  2. Keep your stable install available. Since GoldenCheetah runs on Linux, macOS, and Windows, you can keep the stable 3.8 install in place and test the snapshot separately rather than replacing your working setup.
  3. Expect the unexpected. Snapshot builds are published automatically, so a build may appear without a formal announcement beyond the snapshot page.

What you gain and what you risk

You gain: early access to significant new enhancements and fixes for major bugs, without waiting for the next stable release.

You risk: regressions — features that worked in the stable release may behave differently or fail. Because snapshots are developer-tested only, edge cases in your specific device imports or analysis workflows are less likely to have been caught.

A practical approach

If you depend on GoldenCheetah for regular analysis of ride data imported from devices such as Garmin/ANT+ (FIT, FIT 2.0), PowerTap (RAW, CSV), SRM (SRM), or cloud services like Strava, Dropbox, and Google Drive, treat snapshots as a testing channel rather than your primary tool. Run them on a copy of your data, verify that your import formats and charts still work, and only then consider adopting the changes — or simply wait for them to land in the next stable release.

If you are troubleshooting a specific bug that a snapshot claims to fix, the snapshot is worth trying — with a backup in place and the expectation that other things may break.