Releases

Releases

Every tag, automatically.

Auto-generated feed of every released version. New tags land here within seconds of being cut. For the curated narrative on what each release means, see the changelog.

Release timeline

v1.8.272026-06-23
v1.8.282026-06-23
v1.8.292026-06-23
v1.8.302026-06-23
v1.8.312026-06-25
v1.8.322026-06-27
v1.8.332026-06-27
v1.8.342026-06-27
v1.8.352026-06-27
v1.8.362026-06-27
v1.8.372026-06-27
v1.8.382026-06-27
v1.8.392026-06-27
v1.8.402026-06-28
v1.8.412026-06-29
v1.8.422026-07-01
v1.8.432026-07-02
v1.8.442026-07-02
v1.8.452026-07-03
v1.8.462026-07-03
v1.8.472026-07-03
v1.8.482026-07-09
v1.8.492026-07-09
v1.8.502026-07-09
v1.8.512026-07-10
v1.8.522026-07-10
v1.8.532026-07-10
v1.8.542026-07-10
v1.8.552026-07-10
v1.8.562026-07-11

Every entry below is a real Git tag from the source repository. The pipeline is push-based: when a tag is published, our CI signs an HMAC payload and POSTs it to a webhook here, which upserts the release as a draft for human review. Curated language gets edited where it matters; everything else passes through with the original release notes intact. Links back into the source repository are stripped at render time because the repository itself is private — what you see is the work, not a pointer to the code.

The hourly poll is a fallback in case a webhook is missed. The latest tag usually lands within five seconds of being cut; if the webhook drops we’ll pick it up on the next poll cycle. The three things you might want elsewhere: the changelog bundles releases into the narrative of what shipped and why, the status page shows engineering pulse (commit heatmap, open work, CI runtime), and individual GitHub release URLs are intentionally omitted — the source isn’t public. Email beta@snapshotscoring.com if you want a TestFlight or Play Store invite.

Versioning follows semver: MAJOR.MINOR.PATCH. Major bumps mean breaking changes on the wire (mobile app or WordPress plugin), minor bumps add features without breaking older clients, and patch bumps are bug fixes only. The pipeline auto-versions from main; commit messages tagged feat: trigger a minor bump, fix: a patch, BREAKING CHANGE a major. Releases are tested against the production API on real iOS and Android devices via Maestro before they’re cut, and CI gates merging to main with a Django backend test suite, an iOS E2E run, an Android E2E run, and a CodeQL security scan.

2026-07-11 RELEASEv1.8.56

v1.8.56

2026-07-10 RELEASEv1.8.55

v1.8.55

2026-07-10 RELEASEv1.8.54

v1.8.54

2026-07-10 RELEASEv1.8.53

v1.8.53

2026-07-10 RELEASEv1.8.52

v1.8.52

2026-07-10 RELEASEv1.8.51

v1.8.51

2026-07-09 RELEASEv1.8.50

v1.8.50

2026-07-09 RELEASEv1.8.49

v1.8.49

2026-07-09 RELEASEv1.8.48

v1.8.48

2026-07-03 RELEASEv1.8.47

v1.8.47

2026-07-03 RELEASEv1.8.46

v1.8.46

2026-07-03 RELEASEv1.8.45

v1.8.45

2026-07-02 RELEASEv1.8.44

v1.8.44

2026-07-02 RELEASEv1.8.43

v1.8.43

2026-07-01 RELEASEv1.8.42

v1.8.42

2026-06-29 RELEASEv1.8.41

v1.8.41

2026-06-28 RELEASEv1.8.40

v1.8.40

2026-06-27 RELEASEv1.8.39

v1.8.39

2026-06-27 RELEASEv1.8.38

v1.8.38

2026-06-27 RELEASEv1.8.37

v1.8.37

Looking for more context?

The story behind each release.

This page lists every tag. The changelog groups them into the work that mattered — what landed, why, and what’s next. The status page has the live engineering pulse — commit heatmap, open work, CI runtime.