Skip to content

Bump submodules to decouple LoopKit and LoopAlgorithm - #568

Merged
ps2 merged 2 commits into
next-devfrom
bump/plain-numbers-split
Nov 2, 2026
Merged

ps2 merged 2 commits into
next-devfrom
bump/plain-numbers-split

Conversation

@ps2

@ps2 ps2 commented Nov 1, 2026 •

Copy link
Copy Markdown
Contributor

Bumps the submodules to their branch tips. The main change makes LoopKit and LoopAlgorithm independent of each other, so LoopKit can be used without building LoopAlgorithm. These submodules have to move together.

Decoupling LoopKit and LoopAlgorithm

Slow retrospective correction and Guard + Runway v2

Also landed since the last bump

Testing

LoopKit no longer depends on LoopAlgorithm, and LoopAlgorithm takes plain
numbers in fixed units. Loop bridges the two. Also picks up everything else
that has landed on the submodule branches.
dabear pushed a commit to dabear/LoopWorkspace that referenced this pull request Nov 1, 2026
…m LoopKit (LoopKit #674, Loop #2635)

LoopKit and Loop review branches with those upstream changes merged in; the
watch host reads predicted glucose through LoopKit's values.
dabear pushed a commit to dabear/LoopWorkspace that referenced this pull request Nov 2, 2026
dabear pushed a commit to dabear/LoopWorkspace that referenced this pull request Nov 2, 2026
…ew-pr-plus-local-changes

The review branch is rewritten on current next-dev (LoopKit#568's current head), with remote actions in their own commit. LoopAlgorithm goes back to upstream, dropping the negative insulin damper fork. Kept: the bundle ID, critical alerts, Garmin listed as coming soon, and Loop on its personal branch.
@dabear dabear mentioned this pull request Nov 2, 2026
@ps2
ps2 merged commit fc5194f into next-dev Nov 2, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant