LoopKit · marionbarker · Sep 15, 2026 · Sep 12, 2026 · Sep 14, 2026 · Sep 14, 2026
diff --git a/docs/browser/automatic.md b/docs/browser/automatic.md
@@ -2,16 +2,42 @@
 
 The instructions provided for building with a browser include settings to automatically update and build for you.
 
-## Manual Action for Automatic Build
+## Automatic Build
 
-!!! warning "Browser Build for *Loop* Disabled?"
-    We do not know why, but GitHub is disabling the Build Loop Action for LoopWorkspace even though the repository is not stale.
+!!! tip "Automatic Build Returns for Loop v3.14.7 and newer"
+    With v3.14.7, a new file name is used for automatic building using the Browser Build method.
+
+    * The new file: build_loop_auto.yml has the same content as the older build_loop.yml
+        * It appears that just giving it a new name was enough to prevent GitHub from disabling the build process
+        * Once you update to v3.14.7, your automatic building will be restored
+    * The old file: build_loop.yml is still in your LoopWorkspace folder for your convenience
+        * It no longer has the instructions to run automatically (that did not work anyway)
+        * If you had customization lines in build_loop.yml, they should still be there
+        * Simply copy those lines from build_loop.yml to build_loop_auto.yml to transfer the customization instructions to the file that actually runs to build Loop once a month
+
+The Actions shown for Loop were modified with the v3.14.7 release. The new build_loop_auto.yml file shows up as *Build Loop Auto* and actually runs every Sunday. The existing build_loop.yml shows up as *Build Loop Manual*. It can still be run manually, but it no longer is triggered automatically and continues to show as Disabled.
+
+![the new build loop auto is automatic](img/build-loop-auto.svg ){width="400"}
+{align="center"}
+
+## Skipped Build
 
-    If this is happening to you, see [What Manual Action is Required?](#what-manual-action-is-required).
+The automatic build process checks once a week for updates to the `main` branch. If there are no updates, it skips the build unless it is the second Sunday of the month.
 
-    * The automatic build actions should occur every Sunday
-        * The automatic build using the same code works for all OS-AID apps except for *Loop*
-        * See this [GitHub Discussion topic for details](https://github.com/orgs/community/discussions/181236)
+* The skipped build used to show a green check mark which caused some confusion
+* With v3.14.7, the indications were updated as shown in the graphic below
+    * top row: a scheduled build was successful (this one was the second Sunday of a month)
+    * middle row: the build was manually triggered and was successful
+    * bottom row: a schedule run of the build_loop_auto file, determined there was no reason to build, the icon shows the build was skipped
+
+![clear indication if build was skipped or successful](img/build-skip-or-success.svg ){width="300"}
+{align="center"}
+
+
+## Manual Action for Automatic Build
+
+!!! warning "Browser Build for *Loop* Disabled?"
+    GitHub disables the Build Loop Action for LoopWorkspace for v3.14.2 and older. Please update your fork to bring in the changes for v3.14.7 (or newer).  See: [Automatic Build](#automatic-build)
 
 ??? tip "Stale Repositoriy Always Requires Manual Action (Click to Open Close)"
     *GitHub* automatically **disables actions** that run according to a schedule if the repository in question is **inactive**.

diff --git a/docs/browser/img/build-loop-auto.svg b/docs/browser/img/build-loop-auto.svg
diff --git a/docs/browser/img/build-skip-or-success.svg b/docs/browser/img/build-skip-or-success.svg
diff --git a/docs/build/pump.md b/docs/build/pump.md
@@ -1,13 +1,13 @@
 ## Compatible Pump
 
 !!! info "Time Estimate"
-    - Omnipod users: 3 seconds to remember which Personal Diabetes Manager (PDM) you've been using.
+    - Omnipod users: All Omnipod Pod Types are compatible
     - Medtrum Nano users: both 200 U and 300 U patches are supported
     - Medtronic users: 10 minutes to put a battery in and look at model and firmware
     - Dana users: you must be willing to build a feature branch and understand the known issues
 
 !!! abstract "Summary"
-    - If you use [Omnipod](#omnipod-pumps) - check which kind
+    - If you use [Omnipod](#omnipod-pumps) - your pump is supported
     - If you use [Medtrum Nano](#medtrum-nano) - your pump is supported
     - If you have a Medtronic pump, check the [Medtronic Pump Version](#check-medtronic-pump-version) list to ensure compatible model/firmware
     - For expert testers only, must build a special branch:
@@ -26,10 +26,10 @@
 
 These types of pumps are compatible with the *Loop* app.
 
-* [Omnipod Eros Pods](pump.md#omnipod-pumps)
+* [Omnipod Classic (or Eros) Pods](pump.md#omnipod-pumps)
 * [Omnipod DASH Pods](#omnipod-dash)
     * See caveat about [iPhone 16 and 17e](phone.md#compatible-device){: target="_blank" }
-* [Omnipod 5 Pods](#omnipod-5) only available in development branches
+* [Omnipod 5 Pods](#omnipod-5)
 * [Medtrum Touchcare Nano](#medtrum-nano) (v3.14.2 or newer)
 * [Older Medtronic pumps](pump.md#check-medtronic-pump-version)
 
@@ -73,12 +73,7 @@ The DASH system has the newer, slimmer locked-android Personal Diabetes Manager
 
 ### Omnipod 5
 
-Loop does not support Omnipod 5 Pods in the released code.
-
-* There is an on-going public beta test with Omnipod 5
-* You must build a development branch to test Omnipod 5 - we encourage most people to wait while experienced users test this implementation
-    * Be sure to read the [Omnipod 5 FAQs](../faqs/omnipod-faqs.md#is-omnipod-5-available-for-open-beta-testing){: target="_blank" }
-    * See [Updates in dev](../version/development.md#updates-in-dev){: target="_blank" } if you are an experienced user who wants to help with testing and are willing to build frequently and report any issues to the development team
+!!! success "Omnipod 5 Pods are supported with released code v3.14.7 or newer"
 
 - - -
 

diff --git a/docs/faqs/cgm-faqs.md b/docs/faqs/cgm-faqs.md
@@ -139,7 +139,7 @@ If you prefer not to customize Loop, then you can configure [Nightscout](https:/
 
 ## Can I use Eversense E3 or Eversense 365?
 
-With `dev` branch, 3.14.2 and later, Eversense is included in the Loop build.
+For Loop versions 3.14.2 and newer, Eversense is included.
 
 ## Can the *Loop* app read CGM data from Nightscout?
 

diff --git a/docs/faqs/loop-faqs.md b/docs/faqs/loop-faqs.md
@@ -229,7 +229,6 @@ For Eros Pod users, your Pod will finish any currently running temporary basal r
 Hey now...let's be grateful for what we have first. The ability to use the *Loop* app is the result of tremendous amounts of effort, time, and sacrifice by volunteers. Reverse engineering the pumps' communication protocols for any Open-Source Automated Insulin Delivery (OS-AID) system use is a large undertaking. You don't need to let us know that you'd love to see more pumps compatible with Loop; we know that. There is just an awful lot of work that needs to happen and it is neither quick nor easy.
 
 * Tandem pumps are not compatible (yet)
-* Omnipod 5 pods are compatible with Loop-dev and Loop-next-dev
 * Dana pumps are available using a feature branch
 * Newer Medtronic pumps are not compatible