diff --git a/docs/browser/automatic.md b/docs/browser/automatic.md index 8113839a4d8..3e6f2b4d30e 100644 --- a/docs/browser/automatic.md +++ b/docs/browser/automatic.md @@ -12,11 +12,18 @@ The instructions provided for building with a browser include settings to automa * **inactive** means stable code (no new commit within the last 60 days) * **disables actions** means the Build Action shows up as disabled +!!! warning "Browser Build Disabled" + We do not know why, but GitHub is disabling the Build Loop Action for LoopWorkspace even though the repository is not stale. + + * We think it is associated with running too many builds at a busy time that requested too many runners (virtual computers) + * The redesigned build action for v3.8.2 should alleviate this + * We also plan to reach out to GitHub after people have transitioned to the v3.8.2 build schedule + ### What Manual Action is Required? -For any repository that is stable, like the *Loop* app, you may need to take manual action to keep automatic builds flowing every month. +For any repository that shows the build action disabled, you should enable the action and do a manual build. -* Put a calendar reminder to check every month on the 2nd day of the month (or later) +* Put a calendar reminder to check every month on the 15th day of the month (or later) * Check that *TestFlight* has a new build of the *Loop* (or other) app * If not, go to your repository to see if the build action is disabled * If necessary, enable the build action at your repository as shown in the graphic below and then launch a manual build @@ -27,6 +34,10 @@ This keeps the most recent version of your app available in *TestFlight* for you > Builds in *TestFlight* are good for 90 days before they [expire](../operation/features/notifications.md#loop-app-expiration-notification){: target="_blank" }. +Your build may fail for other reasons - most common is forgetting to sign your updated license agreement or not adding the variable needed to get automatic annual certification renewal. + +* Head over to [Errors with Browser](bb-errors.md){: target="_blank" } + ## What is Automatic These events are automatically scheduled: @@ -50,11 +61,51 @@ You still need to **take these actions** to ensure a recent build of the *Loop* * Check your *GitHub* action if you ever get an email saying an automatic action failed * Look at your *TestFlight* app on the second of every month to make sure a new build is available for you to install when you are ready +### Modified Design for Build Action + +The modified design for the build action found in `Loop v3.8.2` and newer is documented in this section. + +#### Updated Build Features + +The code that controls the build process was streamlined and enhanced. It runs every Sunday at a time when *GitHub* is not impacted. The portion of the action that decides whether to build or not completes in a few seconds. + +**Build when** + +* updates are detected +* it is the second Sunday of the month + +**Other features** + +* remove the concept of alive branches +* remove the requirement that your fork name match the upstream repository name +* enable any branch in your fork to be updated if the upstream repository has the same branch + * if you choose to have a special branch in your fork set to default, the automatic check for updates works for that special branch + + +??? question "Do you want to know more? (Click to open/close)" + **Build Action Redesign** + + When GitHub allowed the use of alive branches with automatic addition of commits to the branch, there were extra steps in the build yml file and limitations to which branches would be updated. + + * These steps kept your fork from getting stale + * GitHub will disable your build actions if no commits have been added for 60 days + + Because this trick is no longer allowed, the creation and use of alive branches was removed. That opened the door to streamline and enhance the build action capabilities. + + If you want to follow the detailed design steps taken to reach this new version, see the following LoopFollow PR. (Most people do not need to know this). + + * [LoopFollow PR 465: Shift GitHub to check for updates every Sunday and build 2nd Saturday of each month](https://github.com/loopandlearn/LoopFollow/pull/465) + * [LoopFollow PR 470: Update the GitHub build schedule to every Sunday](https://github.com/loopandlearn/LoopFollow/pull/470) + * [LoopFollow PR 477: Revise Browser Build to Remove Alive Branches](https://github.com/loopandlearn/LoopFollow/pull/477) + * [LoopFollow PR 480: Expand and streamline build action](https://github.com/loopandlearn/LoopFollow/pull/480) + ### Successful Weekly Action -Normally, you will see a successful `build action` once a week. This happens every Wednesday. +Normally, you will see a successful `build action` once a week. This happens every Sunday (as soon as your version is 3.8.2 or newer). + +> Previously the build action would run every Wed or the first of the month, when GitHub resources were impacted. -If there are no updates to the `main` branch, your actions show a very short, successful `build action` as shown in the graphic below. It only takes about a minute because the logic says - no update then skip the build. +If there are no updates to the `main` branch, your actions show a very short, successful `build action` as shown in the graphic below. It only takes a few seconds because the logic says - if no update was detected and it is not the second Sunday, then skip checking the certificates and skip the build. ![normal weekly check for updates when there are no updates](img/normal-check-for-updates.png) @@ -64,7 +115,9 @@ In that case, you should check your favorite information site to find out what t ### Successful Monthly Action -On the first day of every month, you will see a successful `build action`. The purpose of this build is to provide a recent version of the app in *TestFlight* so you are never in a situation where you have no app on your phone. +On the second Sunday of every month, you will see a longer `build action`. The purpose of this build is to provide a recent version of the app in *TestFlight* so you are never in a situation where you have no app on your phone. + +> Previously the build action would run every Wed or the first of the month, when GitHub resources were impacted. !!! important "You Get No Warning if Repository Build Action is Disabled" If your build action is disabled, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped. @@ -75,35 +128,16 @@ You start getting [Notifications](../operation/features/notifications.md#loop-ap ### What are the `alive branches`? -The automatic update and build feature is embedded in the build_loop.yml code and uses the GitHub scheduling feature to trigger actions to run automatically. - -One or more branches are added to your repository that start with the name `alive`. Don't worry about these. They are automatically created so GitHub will keep building your app automatically. - -* GitHub keeps track of repositories -* If there is no activity in a given repository in 60 days, GitHub disables Actions -* If your Actions are disabled, you don't get automatic builds -* Clever people developed a work around for this - -You may see branches called `alive`, `alive-dev` or `alive-main` in your repository. - -The `alive` branches are there so at least one commit per month is added to an `alive` branch in your repository. That keeps your repository active to allow the automatic update and build process. - -The `alive` branches are only used for the keep-alive functions. Do not build using an `alive` branch. Most people will build using the default branch of `main`. - -#### Automatic Creation of `alive branch` +In April 2025, GitHub disallowed using the build action to automatically add commits to `alive branches`. This trick was previously used to keep your fork active even when the upstream repository was stable. -The `alive` branch you need is created automatically when you run the `Build Loop` action. +Once you update to v3.8.2 or newer, references to `alive branches` are removed from the build action. -!!! warning "I got an error regarding a branch with `alive` in the name" - * Sometimes you get an error about an `alive` branch - * If you do get an error, simply delete the branch and run the `Build Loop` action again - * Use this [GitHub link](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-and-deleting-branches-within-your-repository#deleting-a-branch) or ask for help when deleting a branch - * You can delete every branch that starts with the name `alive` - * Leave the other branches alone unless a mentor directs you to take action +> * If you have alive branches (`alive`, `alive-dev` or `alive-main`) you may delete them if you choose +* Only delete alive branches after your default branch is updated to the new version ## Automatic Certificates -Automatic renewal of certificates is included in `Loop 3.6.0`. +Automatic renewal of certificates is included in `Loop 3.6.0` and newer versions. ### Requirements @@ -134,22 +168,20 @@ Some Open-Source apps, in particular `Trio`, `LoopCaregiver`, `LoopFollow`, `Loo ### Open-Source App Schedule -!!! information "Changes are Coming" - We are in process of modifying when **planned** builds happen. +With the release of `Loop 3.8.2` and newer, the build schedule is updated. - The *LoopFollow* app and *Trio* app are already changed. This change will propagate to other apps in the Open-Source ecosystem. +**New schedule - there will be one automatic run of the build action each week on Sunday.** - New method - there will be one automatic run of the build action each week on Sunday. +* If no updated code is detected, the build will be skipped unless it is the **second Sunday** of the month +* If updated code is detected, the new version of the app will be built and uploaded to TestFlight - * If it is the second Sunday of the month, the app will be built and uploaded to TestFlight - * If updated code is detected, the new version of the app will be built and uploaded to TestFlight - * If no updated code is detected, the build will be skipped (except for the second Sunday of the month) +The table below indicates **planned** time for the automatic build schedule. GitHub will start the build action no earlier than the stated time but it can be delayed depending on activity at GitHub. -The table below indicates **planned** time for the automatic build schedule. For apps not yet changed to the new method, the weekly runs are on Wednesday and the monthly runs are on the 1st of each month. +> For apps not yet changed to the new method, the weekly runs are on Wednesday and the monthly runs are on the 1st of each month. | Open-Source App | AutoCerts? | Weekly
UTC | Once a Month
UTC | |:--|:-:|:-:|:-:| -| Loop | ✅ | 09:33 | 07:33 | +| Loop | ✅ | 07:33 | same | | LoopCaregiver | ✅ | 13:33 | 11:33 | | LoopFollow | ✅ | 10:17 | same | | LoopFollow_Second | ✅ | 10:27 | same | @@ -202,7 +234,7 @@ This is an optional step. If you are happy with the automatic sync and update, y Note that the weekly and monthly `Build Loop` actions will continue, but the actions are modified if one or more of these variables is set to false. **A successful Action Log will still appear, even if no automatic activity happens**. - * If you want to manually decide when to update your repository to the latest commit, but you want the monthly builds and keep-alive to continue: + * If you want to manually decide when to update your repository to the latest commit, but you want the monthly builds to continue: * create the variable `SCHEDULED_SYNC` and set it to false * either do not create the variable `SCHEDULED_BUILD` or set it to true * If you are building the `dev branch` at a time when there is a lot of activity in that branch, you may want this configuration @@ -214,10 +246,10 @@ This is an optional step. If you are happy with the automatic sync and update, y |
`SCHEDULED_SYNC`
|
`SCHEDULED_BUILD`
| Automatic Actions | |---|---|---| - | `true` (or N/A) | `true` (or N/A) | This is the default:
keep-alive, weekly update check (auto update/build), monthly build with auto update| - | `false` | `true` (or N/A) | keep-alive, monthly build, no auto update | - | `true` (or N/A) | `false` | keep-alive, weekly update check with auto update, only builds if update detected | - | `false` | `false` | no automatic activity, no keep-alive| + | `true` (or N/A) | `true` (or N/A) | This is the default:
weekly update check (auto update/build), monthly build with auto update| + | `false` | `true` (or N/A) | monthly build, no auto update | + | `true` (or N/A) | `false` | weekly update check with auto update, only builds if update detected | + | `false` | `false` | no automatic activity| ### How to configure a variable @@ -241,10 +273,9 @@ Your build will run on the following conditions: - Default behaviour: - Run weekly, every Wednesday at 08:00 UTC to check for changes; if there are changes, it will update your repository and build - Run monthly, every first of the month at 06:00 UTC, if there are changes, it will update your repository; regardless of changes, it will build - - Each time the action runs, it makes a keep-alive commit to the `alive` branch if necessary -- If you disable any automation (both variables set to `false`), no updates, keep-alive or building happens when `Build Loop` runs -- If you disabled just scheduled synchronization (`SCHEDULED_SYNC` set to`false`), it will only run once a month, on the first of the month, no update will happen; keep-alive will run -- If you disabled just scheduled build (`SCHEDULED_BUILD` set to`false`), it will run once weekly, every Wednesday, to check for changes; if there are changes, it will update and build; keep-alive will run +- If you disable any automation (both variables set to `false`), no updates or building happens when `Build Loop` runs +- If you disable only scheduled synchronization (`SCHEDULED_SYNC` set to`false`), the build action runs weekly but your fork is not updated and the monthly build uses the current version of your fork +- If you disable only scheduled build (`SCHEDULED_BUILD` set to`false`), the build action runs weekly to check for changes; if there are changes, it will update and build ### Disable Automatic Actions diff --git a/docs/browser/bb-errors.md b/docs/browser/bb-errors.md index 5f4ec5e7242..1024a99dc3f 100644 --- a/docs/browser/bb-errors.md +++ b/docs/browser/bb-errors.md @@ -154,26 +154,6 @@ Ignore the warnings - this does not affect the build. ## Rebuild Errors: Quick Reference -### `Check Upstream and Keep Alive` Error - -!!! important "`Check Upstream and Keep Alive` Error" - **Error**: Your Browser Build fails and when you click on the link, you see - - * **`Check Upstream and Keep Alive`** failed - - **Consequence**: any required sync of your fork is skipped and build is skipped - - **Solution**: - - * Manually sync your fork of the repository: [Update `Fork`](bb-update.md#update-fork){: target="_blank" } - * Manually start your build: [Build](bb-update.md#build-the-app){: target="_blank" } - - **Details about what happened**: - - On 21 April 2025, *GitHub* removed one of the third-party repositories that we used to keep automatic building going without action on your part. The repository was removed because it was in violation of the *GitHub* terms of service. *GitHub* disables automatic actions for repositories that have been inactive (no commits added in 60 days). For stable apps, like the *Loop* app, this third-party repository enabled a workaround to keep the builds happening. - - This affected all the Open-Source apps in our community - Loop, LoopFollow, LoopCaregiver, Trio, iAPS and xDrip4iOS. The developers in our community have restored the ability to build using the Browser Build method. Stay tuned for updates to required actions in the documentation over the next few months, before we hit the 60 day limit. - ### Manual Enable for Build Action May be Required The automatic build actions continue to happen on schedule, but starting May 2025, you may find your build action disabled by *GitHub*. (This might happen every 60 days, but it might happen sooner.) In that case, no build actually happens, no warning email is sent and a green checkmark (✅) appears beside a very short build action in which the actual build was skipped. @@ -223,9 +203,6 @@ These are some of the most common errors to date. 1. You skipped running one of the actions 1. You need to sign a program license agreement or update a credit card at Apple Developer * Be sure to read [Misleading Error Message](#misleading-error-message) -1. You got an error regarding a branch with `alive` in the name - * You can delete any branch that starts with the name `alive` and try again - * See [Automatic Creation of `alive branch`](automatic.md#automatic-creation-of-alive-branch){: target="_blank" } ## Examine Annotation diff --git a/docs/build/pump.md b/docs/build/pump.md index 160d2278d46..f36a4000fa2 100644 --- a/docs/build/pump.md +++ b/docs/build/pump.md @@ -3,14 +3,14 @@ !!! info "Time Estimate" - Omnipod users: 3 seconds to remember which Personal Diabetes Manager (PDM) you've been using. - Medtronic users: 10 minutes to put a battery in and look at model and firmware - - Dana users: 5 minutes to check your model number - Other pump users: 5 days to email friends asking them to check closets for their old Medtronic pump or call your insurance to start prior authorization for Omnipod !!! abstract "Summary" - If you have a Medtronic pump, check the [Medtronic Pump Version](#check-medtronic-pump-version) list to ensure compatible model/firmware - If you use [Omnipod](#omnipod-pumps) - check which kind - - If you use [Dana](#sooil-dana-pumps) - check which kind - - If you use [Medtrum Nano](#medtrum-nano) - Check which loop version + - For expert testers only, must build a special branch: + - If you use [Dana](#sooil-dana-pumps) - check which kind + - If you use [Medtrum Nano](#medtrum-nano) - click the link !!! question "FAQs" - **"How can I find a compatible Medtronic pump?"** Refer to [Finding a Medtronic Pump](#finding-a-medtronic-pump). @@ -27,8 +27,11 @@ These types of pumps are compatible with the *Loop* app. * [Omnipod Eros pumps](pump.md#omnipod-pumps) * [Omnipod DASH pumps](#omnipod-dash) * See caveat about [iPhone 16](phone.md#compatible-device){: target="_blank" } -* [Dana-i / DanaRS-v3](#sooil-dana-pumps) (v3.7.5 or newer) -* [Medtrum Touchcare Nano](#medtrum-nano) (feat/dev-medtrum branch only, v3.9.0 or newer) + +You must build a special branch to test these pumps. Please only test if you are willing to update frequently, pay close attention and return to open loop as needed. + +* [Dana-i / DanaRS-v3](#sooil-dana-pumps) (experts only, work in progress) +* [Medtrum Touchcare Nano](#medtrum-nano) (experts only, work in progress) ## Check Medtronic Pump Version @@ -192,10 +195,10 @@ Loop does not support Omnipod 5 pods. ## Sooil Dana pumps -!!! warning "Dana pumps support is new - pay attention" - The Dana pump is supported with the released *Loop* app, v3.8.0 or newer. +!!! warning "You must build `feat/dev-dana-medtrum` branch to use Dana pumps" + This branch is experimental and requires careful attention to bolus accounting and IOB reporting. - Follow the [Zulipchat Dana Pump discusion](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/DanaKit.20support.20for.20Loop) if you need additional support for the Dana pump. + * You must follow [zulipchat DanaKit topic](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/DanaKit.20Troubleshooting/with/547829260) Read these pages in LoopDocs: @@ -208,7 +211,7 @@ Loop does not support Omnipod 5 pods. The Dana-i is the latest and greatest from the Korean pump manufacturer Sooil, released in 2020. -> The *Loop* app v3.7.5 or newer supports the Dana-i. +> The `feat/dev-dana-medtrum` branch supports Dana-i. ![Dana-i](img/dana-i.png){width="250"} {align="center"} @@ -218,19 +221,21 @@ The Dana-i is the latest and greatest from the Korean pump manufacturer Sooil, r The DanaRS was first released in 2002, with firmware version v1 which is not supported at this time. Only firmware version v3 and onwards are supported with the *Loop* app. [Check here](../loop-3/add-pump.md#dana-i-danars-v3) to see how to check your firmware version. -> The *Loop* app v3.7.5 or newer supports the DanaRS-v3. +> The `feat/dev-dana-medtrum` branch supports DanaRS-v3. ![DanaRS-v3](img/danars.png){width="250"} {align="center"} ## Medtrum Nano -!!! warning "You must build feat/dev-medtrum branch to use Medtrum patch pumps" - The Medtrum patch pump is in feat/dev-medtrum (as of version v3.9.0) and is experimental as of now. +!!! warning "You must build `feat/dev-dana-medtrum` branch to use Medtrum pumps" + This branch is experimental and requires careful attention to bolus accounting and IOB reporting. + + * You must follow [zulipchat Medtrum channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Medtrum.20Nano.20-.20pumps.20for.20development.20use/with/481836247) - **Be very careful running this. The initial version had a bug where a delivered bolus was not always recorded properly. This is just one example of why only experts should volunteer to test experimental code.** + Read this section in LoopDocs: - Follow along in the [zulipchat Medtrum channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Medtrum.20Nano.20-.20pumps.20for.20development.20use/with/481836247). + * [Medtrum Nano](../loop-3/add-pump.md#medtrum-nano){: target="_blank" } !!! info "All versions are supported!" Both 200U (MD0201 & MD8201) and 300U (MD8301) version are supported with the correct version of the *Loop* app. diff --git a/docs/build/rileylink.md b/docs/build/rileylink.md index b40d4429e1e..f065c6cad94 100644 --- a/docs/build/rileylink.md +++ b/docs/build/rileylink.md @@ -76,7 +76,7 @@ Sections of interest include: ## Waiting for your RileyLink Compatible Device -While you are waiting for the RileyLink compatible device to arrive, you can proceed with these build directions and can try one of the [Simulated Loop](../version/simulator.md){: target="_blank" } options. After that, unless you are using *Omnipod DASH* or Sooil Dana, you'll have to wait for your device. +While you are waiting for the RileyLink compatible device to arrive, you can proceed with these build directions and can try one of the [Simulated Loop](../version/simulator.md){: target="_blank" } options. After that, unless you are using pump that communicates directly with Bluetooth, you'll have to wait for your device. The population of DIY loopers (Loop and Android APS) has grown enough that you might be able to find someone local to loan you their spare. diff --git a/docs/loop-3/add-pump.md b/docs/loop-3/add-pump.md index bfe11e833d6..47718a23805 100644 --- a/docs/loop-3/add-pump.md +++ b/docs/loop-3/add-pump.md @@ -17,9 +17,9 @@ Loopers can choose from 5 pumps and a simulator: * Please refer to [Compatible Pump](../build/pump.md#check-medtronic-pump-version) for additional details * Omnipod * Omnipod DASH -* Dana-i / DanaRS-v3 (v3.7.5 or newer) +* Dana-i / DanaRS-v3 (**work-in-progress; experts only**) * Note: DanaRS-v1 or any Dana Korean versions are not supported -* Medtrum Nano patch pump +* Medtrum Nano patch pump (**work-in-progress; experts only**) * Insulin Pump Simulator !!! info "Omnipod Terms" @@ -53,15 +53,12 @@ Here is an overview of the different steps for adding each pump. Before changin 1. [Select RileyLink](#select-rileylink) 1. [Medtronic](#medtronic) -#### Steps for [Dana-i / DanaRS-v3](#dana-i-danars-v3) +#### Other Pumps -> Requires v3.7.5 or newer - -1. [Select Dana-i/DanaRS-v3](#select-dana-idanars-v3) -1. [Insulin Type](#insulin-type) -1. [Delivery Speed](#delivery-speed) -1. [Pair Dana](#pair-dana) +> Experts only, `feat/dev-dana-medtrum` branch required +* [Dana-i / DanaRS-v3](#dana-i-danars-v3) +* [Medtrum Nano](#medtrum-nano) ## Add Pump @@ -238,6 +235,31 @@ The Medtronic status and commands available are shown in the [Pump Settings](med ## Dana-i / DanaRS-v3 +### Dana in Loop Requires Expert Testing + +**WARNING: Dana support in Loop is a work-in-progress; only experts should consider testing this.** + +> **A pump manager that works for Trio must be separately tested for Loop** + +* Several issues were reported regarding bolus accounting and IOB reporting for Loop +* For this reason, the Dana pump support, available in v3.8.1, was removed from the `main` and `dev` branches for v3.8.2 (3.9.2) +* Please do not use Dana with Loop unless you are willing to test and communicate with [developers on zulipchat in this DanaKit channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/DanaKit.20Troubleshooting/with/547829260) + +### Before Testing Dana + +The branch needed to get Dana in Loop is: `feat/dev-dana-medtrum`. + +This branch is subject to rapid updates. + +Please refer to [zulipchat DanaKit topic](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/DanaKit.20Troubleshooting/with/547829260) before building this branch. + +### When Testing Dana + +!!! warning "You must build feat/dev-dana-medtrum branch to use Dana pumps" + This branch is experimental and requires careful attention to bolus accounting and IOB reporting. + + * You must follow [zulipchat DanaKit topic](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/DanaKit.20Troubleshooting/with/547829260) + !!! info "Support for Dana-i" All versions of the Dana-i are supported at the moment! @@ -355,8 +377,31 @@ Therefore, it is important to check if your CGM provides a heartbeat. If it does ## Medtrum Nano -!!! warning "You must build feat/dev-medtrum branch to use Medtrum patch pumps" - The Medtrum patch pump is in feat/dev-medtrum (as of version v3.9.0) and is experimental as of now + +### Medtrum in Loop Requires Expert Testing + +**WARNING: Medtrum support in Loop is a work-in-progress; only experts should consider testing this.** + +> **A pump manager that works for Trio must be separately tested for Loop** + +* Several issues were reported regarding bolus accounting and IOB reporting for Loop +* For this reason, the Medtrum pump support is only found in a special branch +* Please do not use Medtrum with Loop unless you are willing to test and communicate with [developers on zulipchat in the Medtrum channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Medtrum.20Nano.20-.20pumps.20for.20development.20use/with/481836247) + +### Before Testing Medtrum + +The branch needed to get Medtrum in Loop is: `feat/dev-dana-medtrum`. + +This branch is subject to rapid updates. + +Please refer to the [zulipchat Medtrum channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Medtrum.20Nano.20-.20pumps.20for.20development.20use/with/481836247) before building this branch. + +### When Testing Medtrum + +!!! warning "You must build feat/dev-dana-medtrum branch to use Medtrum patch pumps" + The Medtrum patch pump is experimental and requires careful attention to bolus accounting and IOB reporting. + + * You must follow [zulipchat Medtrum channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Medtrum.20Nano.20-.20pumps.20for.20development.20use/with/481836247) !!! info "All versions are supported!" Both 200U (MD0201 & MD8201) and 300U (MD8301) version are supported with the correct version of the *Loop* app. diff --git a/docs/loop-3/settings.md b/docs/loop-3/settings.md index 550e9defd83..0e03820f768 100644 --- a/docs/loop-3/settings.md +++ b/docs/loop-3/settings.md @@ -160,7 +160,11 @@ The information about the pump section is detailed on several different pages. F * [Add or Modify Pump](add-pump.md) * [Omnipod or Omnipod DASH](omnipod.md) Status and Commands * [Medtronic](medtronic.md) Status and Commands + +For experts only, requires a special branch: + * [Dana Pumps](add-pump.md#dana-i-danars-v3) +* [Medtrum Pumps](add-pump.md#medtrum-nano) ### [CGM Settings](add-cgm.md) diff --git a/docs/troubleshooting/dana-faq.md b/docs/troubleshooting/dana-faq.md index 5dbf17bedc9..b05af28db0c 100644 --- a/docs/troubleshooting/dana-faq.md +++ b/docs/troubleshooting/dana-faq.md @@ -1,5 +1,21 @@ # Dana (RS/-i) FAQ +### Dana in Loop Requires Expert Testing + +**WARNING: Dana support in Loop is a work-in-progress; only experts should consider testing this.** + +> **A pump manager that works for Trio must be separately tested for Loop** + +* Several issues were reported regarding bolus accounting and IOB reporting for Loop +* For this reason, the Dana pump support, available in v3.8.1, was removed from the `main` and `dev` branches for v3.8.2 (3.9.2) +* Please do not use Dana with Loop unless you are willing to test and communicate with [developers on zulipchat in this DanaKit channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/DanaKit.20Troubleshooting/with/547829260) + + +The branch needed to get Dana in Loop is: `feat/dev-dana-medtrum`. + +This branch is subject to rapid updates. + + ## Q: Help I frequently encounter signal loss or orange loops First of all, lets check you CGM, since the dana driver trusts your CGM to provide a heartbeat. diff --git a/docs/version/releases.md b/docs/version/releases.md index a31f814f6e9..18a025f9a94 100644 --- a/docs/version/releases.md +++ b/docs/version/releases.md @@ -8,9 +8,9 @@ For information about version 2 releases and compatibility between version 2 and ## Current Release -The current released version for the *Loop* app is v3.8.1 and is built from the `main` branch of LoopWorkspace. The dates and contents for releases are summarized below in reverse chronological order (so newest release information comes first). +The current released version for the *Loop* app is v3.8.2 and is built from the `main` branch of LoopWorkspace. The dates and contents for releases are summarized below in reverse chronological order (so newest release information comes first). -> When main was updated to v3.8.1 for a hotfix, the same hotfix was applied to the `dev` branch, which is at v3.9.1. +> When main is updated to v3.8.2, the same update is planned for the `dev` branch. It may take a day or two before `dev` is updated to 3.9.2. > See [Updates in `dev`](development.md#updates-in-dev){: target="_blank" } for a summary of difference, if any, between `main` and `dev`. @@ -39,7 +39,61 @@ Releases from `Loop v3.4.4` and older are reported at [*GitHub* _ Please follow these steps to build manually: + +> * [What Manual Action is Required?](../browser/automatic.md#what-manual-action-is-required){: target="_blank" } + +#### Updates in v3.8.2 + +This version updates a few iOS 26 interface issues, moves support for Dana pumps to a different branch, and streamlines and enhances the Browser Build process. + +* Restore expected behavior for phones running iOS 26 + * see [Loop PR 2371](https://github.com/LoopKit/Loop/pull/2371) / [LoopKit PR 573](https://github.com/LoopKit/LoopKit/pull/573) +* Modify the build schedule to run on Sundays and build on the second Sunday of each month + * see [Updated Build Features](../browser/automatic.md#updated-build-features){: target="_blank" } details + +* [Remove DanaKit](#why-was-danakit-support-changed) support from `main` and `dev` branches of the *Loop* app +* Update some translations + +> When main is updated to v3.8.2, the same update is planned for the `dev` branch. It may take a day or two before `dev` is updated to 3.9.2. + +#### Why was DanaKit Support Changed + +> **A pump manager that works for Trio must be separately tested for Loop** + +* Several issues were reported regarding bolus accounting and IOB reporting for *Loop* v3.8.1 +* For this reason, Dana support is only found in 2 special branches + +If you were using Dana with v3.8.1, a branch called `release/3.8.1` was created for your continued use. + +* The `release/3.8.1` branch will remain available while troubleshooting continues +* This branch is meant to support people already using Dana with v3.8.1 who understand how to manage the issues with that version + +If you are an expert and want to use [Dana](../loop-3/add-pump.md#dana-in-loop-requires-expert-testing){: target="_blank" } or [Medtrum](../loop-3/add-pump.md#medtrum-in-loop-requires-expert-testing){: target="_blank" }, the experimental branch is `feat/dev-dana-medtrum` + +* This branch is subject to rapid updates +* Please do not use Dana with Loop unless you are willing to test and communicate with [developers on zulipchat in this DanaKit channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/DanaKit.20Troubleshooting/with/547829260) + +* Please do not use Medtrum with Loop unless you are willing to test and communicate with [developers on zulipchat in the Medtrum channel](https://loop.zulipchat.com/#narrow/channel/144182-development/topic/Medtrum.20Nano.20-.20pumps.20for.20development.20use/with/481836247) + + ### Loop v3.8.1