Skip to content

Trio v0.8.1

Choose a tag to compare

@dnzxy dnzxy released this 29 May 16:30
· 45 commits to main since this release
35499ad

Trio 0.8.1 trio

0.8.1 is a patch release on top of 0.8.0. It adds a new unified Omnipod pump manager, fixes a spurious bolus failure notification, patches a CI security dependency, and ships several telemetry improvements.

Important

Upgrading from 0.8.0? No onboarding wizard or settings reset required. Existing Omnipod users on OmniKit or OmniBLE are unaffected — the new OmnipodKit driver is purely opt-in and is only activated if you explicitly select it when starting a new pod.


What's Changed At A Glance

  • OmnipodKit pump manager — new unified Eros + DASH driver available as "All Omnipod Types" in the Add Pump flow; pod type selected at activation
  • Fix spurious "Bolus failed" notification — algorithm errors after a successful bolus delivery no longer misreport the bolus as failed
  • Telemetry payload improvements — build date format corrected, locale, time zone, and app name added to the check-in payload
  • Fix telemetry daily send — continuous pings now correctly throttle to once per day
  • Security: fastlane 2.235.0 / jwt 3.2.0 — resolves a Dependabot alert for a ruby-jwt empty-key HMAC bypass (CI/release tooling only, no shipped-app code change)

New Features

OmnipodKit Pump Manager (#1157, #1160)

Adds loopandlearn/OmnipodKit as a new submodule and surfaces it in the Add Pump flow as "All Omnipod Types". Unlike OmniKit (DASH-only) and OmniBLE (Eros-only), OmnipodKit handles both pod generations under a single driver — pod type (Eros vs. DASH) is selected at pod activation rather than at the pump manager level.

Existing users are unaffected. OmniKit and OmniBLE remain in place and are not removed. Users already paired to either of those drivers continue without any change; OmnipodKit is only used if explicitly chosen when setting up a new pump.

The submodule includes translated strings and updated issue templates.


Bug Fixes

Fix Spurious "Bolus Failed" Notification After Manual Bolus (#1151)

The post-bolus determineBasalSync() call was nested inside the bolus do/catch block. This meant that any algorithm error occurring after the bolus had already been successfully delivered — such as "Not enough glucose data" during a CGM warm-up period — was incorrectly caught and surfaced as a bolus failure notification, even though the pump had already delivered the dose.

The algorithm refresh is now wrapped in its own independent do/catch, so algorithm errors after delivery can no longer trigger bolusDidFail or a pump error notification.


Telemetry

Telemetry Payload Improvements (#1172)

Several improvements to the anonymous telemetry check-in payload introduced in 0.8.0:

  • Build date format corrected to YYYY-MM-DD with forced English locale, fixing locale-dependent formatting inconsistencies on non-English devices
  • Locale and time zone added to the payload, enabling aggregate regional analysis without identifying individual users
  • App display name hardcoded to Trio in the payload, ensuring custom-named builds (e.g. from third-party builders) are correctly attributed

Fix Telemetry Daily Send (#1173)

Continuous background pings were not being correctly throttled to once per day. The daily send logic is now enforced properly.
Privacy Policy updated to reflect the additional payload fields.


Security

Fastlane 2.235.0 / jwt 3.2.0 (#1173)

Bumps fastlane 2.233.12.235.0, which relaxes its transitive jwt < 3 constraint and allows the resolver to land jwt 3.2.0. This resolves a Dependabot alert for a ruby-jwt empty-key HMAC bypass vulnerability (sibling of CVE-2026-44351).

This affects CI and release tooling only; no shipped app code is involved.


Full List of PRs in 0.8.1

PR Title Author
#1151 Fix spurious "Bolus failed" notification after manual bolus @mountrcg
#1157 Add OmnipodKit submodule @marionbarker
#1160 Chore: update OmnipodKit (translated strings, issue templates) @marionbarker
#1172 Update telemetry payload: fix buildDate format, add locale/TZ/appName @jwoglom
#1173 Trio v0.8.1 patch release @dnzxy

Contributors

@dnzxy, @mountrcg, @marionbarker, @jwoglom


Note: Trio has not been reviewed by the FDA or any other regulatory entity. As with all versions, please use responsibly and in consultation with your healthcare team.