Update dev to 3.14.4

[marionbarker]

Purpose: Prepare for updating dev to version 3.14.4

With this PR, we are preparing for the next update to dev.

Ready for Review

Mark this as ready for review - this is the beginning of steps to make the new method for communicating with DASH and Omnipod 5 pod generally available. The new method appears to decrease the frequency of 203 Faults for DASH and enables the use of Omnipod 5 pods. These features are deemed important enough to push for a release of v3.14.4 with additional updates coming in the next set of updates to dev.

The steps in the release process include:

1. get an approval to merge this PR to dev
2. merge this PR to dev
   • update LoopDocs with updated dev information
3. prepare a PR to bring this change into main
   • update LoopDocs with updated release information

Method

Collect updates to dev branch in this update_dev_to_3.14.4 branch

• When ready and approved, this PR will be merged into dev as version 3.14.4

The Details section of this PR will be updated with each commit added to this PR.
Before each commit is pushed, the build is tested locally with Xcode.

Details

• Bump version to 3.14.4
• Update OmnipodKit
  • fix a long-standing bug in which Pod active time for reset faults was not handled properly for DASH pods
  • fix a new bug caused by the Pod Keep Alive implementation in which RileyLinks were not released and made available for a new pump manager, e.g., Medtronic or Eros
  • update the tests so code will pass ci/circleci testing
• Browser Build support
  • improve clarity: when build is skipped, run is canceled no green check mark is shown; for details, see Mark scheduled runs with nothing to build as cancelled instead of successful #472
• Update CGMBLEKit
  • Add support for Anubis transmitters for G6 users (thanks to the Trio devs for providing this update)
• Update EversenseKit
  • fix: navigation titles;
  • chore: remove CryptoSwift dependency;
  • style: add loader to calibration
• Update Loop:
  • fix LiveActivityManager bug (see Fix Live Activity cooperative-pool starvation deadlock Loop#2465)
  • this could cause Loop to become unresponsive
• Update MedtrumKit:
  • incorporate Manual Temp Basal
  • fix some issues: prevent double callback, sync collision
    • for details, see the MedtrumKit repository for changes since 24 June 2026
• Update EversenseKit: implement LoopKit alerts, fix: prevent crash after disconnect
• Update Loop, LoopKit and OmnipodKit to use new BLE management
  • The Loop and LoopKit changes are merged to LoopKit dev branches
  • The OmnipodKit branch is still in PR form (see Backport the Omnipod BLE Heartbeat API from next-dev loopandlearn/OmnipodKit#118), but has undergone extensive testing
  • Once we get more testing of this method, OmnipodKit PR 118 will be merged and the SHA updated for this PR
  • (Broke my rule and did not build before I pushed. We need another PR for Loop to bump watch deployment to match a change to LoopKit. While that is open, point to the PR branch so the code will build.)
• Update fastlane to 2.237.0
• Update MedtrumKit again
  • Note that MedtrumKit is under development (the dev branch of MedtrumKit is not ready for use yet)
  • Update to what @bastiaanv says is the last stable commit ( f5daa6e) which include the Manual Temp Basal feature
  • There are open issues in MedtrumKit, but this is an improvement over earlier versions
• Update OmnipodKit: fix a critical, intermittent bug, OmnipodKit PR 124: Backport to dev: Fix self-inflicted connect→cancel→reconnect loop in connect-on-demand
  • This prevents an intermittent state where the OS-AID could not reach the Pod
  • This fix in now found in this branch as well as the next-dev branch for Loop
• Update OmnipodKit: fix a critical, intermittent bug, OmnipodKit PR 128: Fix backport: re-entrant managerQueue deadlock surfacing a pod alert from an advert
• Accept community member PR Clarify scheduled build documentation #466
  • update fastlane/testflight.md CONTRIBUTING.md

[ps2]

This is bringing in some new changes, which is fine; but I was thinking maybe this was just going to prep dev for release to main. With new changes on dev, it should sit on dev for at least a bit.

• EversenseKit has new changes, but seems to be pointing to an older rev 7d07893, not the latest?
• Loop not pointing to the latest dev, either. Missing XCode 27 + Liquid glass fixes.
• MedtrumKit changes don't appear to be commits from the main jbr7rr/MedtrumKit/dev branch? What branch are these commits from in that repo?

[marionbarker]

Timing

I do expect this to sit on dev for a while before it is released to main - I have not started the LoopDocs updates yet that are required to be ready to take the step after this one:

• need to prepare the PR that will merge dev into main
• need to prepare PR for LoopDocs
• these two PR will be merged on the same day in the future when the release happens

Test status

The update_dev_to_3.14.4 branch has been out there for a while and announced on zulipchat which each update.

We are in a situation where we are telling people who are getting 203 Faults with DASH to build this interim branch. I'd like to get those people on main and off a development branch. (Not the standard method of operating.)

Submodule status

The following submodules are not at the tip of their respective repository:

• Ahead of main:
  • OmnipodKit is pointing to the tip of the dev branch (not the main branch) but this is the correct commit for this interim update
  • Any decision regarding branch management for OmnipodKit can be undertaken elsewhere
• Not at the tip and should be (these will be updated)
  • G7SensorKit
  • Loop
• Not at the tip because the tip testing is in process, so I decided (in consultation with @bastiaanv) to point to the last stable commit (this decision is several weeks old)
  • MedtrumKit: do not update at this time from f5daa6e, tip is 2720af0 with testing in-progress
• Not at the tip because the tip has changed and I haven't tested the update (open for discussion)
  • EversenseKit: tip is cc19127, last tested commit is b46c45c

Other updates

Typically I would bring in updates to translations at this time and there are additional improvements to OmnipodKit and MedtrumKit that are close to being ready.

As soon as this PR is merged, I anticipate beginning the work for an update_dev_to_3.14.5 branch.