Deploying to gh-pages from @ 466170d 🚀

Author: marionbarker

browser/automatic/index.html

@@ -1168,7 +1168,40 @@
     </span>
   </a>
 
-    <nav class="md-nav" aria-label="Overview">
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#manual-action-for-automatic-build" class="md-nav__link">
+    <span class="md-ellipsis">
+      Manual Action for Automatic Build
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Manual Action for Automatic Build">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#what-manual-action-is-required" class="md-nav__link">
+    <span class="md-ellipsis">
+      What Manual Action is Required?
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#what-is-automatic" class="md-nav__link">
+    <span class="md-ellipsis">
+      What is Automatic
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="What is Automatic">
       <ul class="md-nav__list">
 
           <li class="md-nav__item">
@@ -3586,7 +3619,40 @@
     </span>
   </a>
 
-    <nav class="md-nav" aria-label="Overview">
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#manual-action-for-automatic-build" class="md-nav__link">
+    <span class="md-ellipsis">
+      Manual Action for Automatic Build
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="Manual Action for Automatic Build">
+      <ul class="md-nav__list">
+        
+          <li class="md-nav__item">
+  <a href="#what-manual-action-is-required" class="md-nav__link">
+    <span class="md-ellipsis">
+      What Manual Action is Required?
+    </span>
+  </a>
+  
+</li>
+        
+      </ul>
+    </nav>
+  
+</li>
+      
+        <li class="md-nav__item">
+  <a href="#what-is-automatic" class="md-nav__link">
+    <span class="md-ellipsis">
+      What is Automatic
+    </span>
+  </a>
+  
+    <nav class="md-nav" aria-label="What is Automatic">
       <ul class="md-nav__list">
 
           <li class="md-nav__item">
@@ -3734,7 +3800,32 @@ <h1>Automatic Update & Build</h1>
 
 <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Anchor link to this Header on this Page">&para;</a></h2>
 <p>The instructions provided for building with a browser include settings to automatically update and build for you.</p>
-<p>This keeps the most recent version of the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app available in <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> for you to install when you are ready.</p>
+<h2 id="manual-action-for-automatic-build">Manual Action for Automatic Build<a class="headerlink" href="#manual-action-for-automatic-build" title="Anchor link to this Header on this Page">&para;</a></h2>
+<div class="admonition important">
+<p class="admonition-title">Automatic Build Requires Manual Action</p>
+<p><em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> automatically <strong>disables actions</strong> that run according to a schedule if the <abbr title="contains project files and each file's revision history">repository</abbr> in question is <strong>inactive</strong>.</p>
+<p>What does that mean?</p>
+<ul>
+<li><strong>inactive</strong> means stable code (no new <abbr title="a formal change to files in a repository; each commit has an alphanumeric identifier (SHA-1)">commit</abbr> within the last 60 days)</li>
+<li><strong>disables actions</strong> means the Build Action shows up as disabled</li>
+</ul>
+</div>
+<h3 id="what-manual-action-is-required">What Manual Action is Required?<a class="headerlink" href="#what-manual-action-is-required" title="Anchor link to this Header on this Page">&para;</a></h3>
+<p>For any <abbr title="contains project files and each file's revision history">repository</abbr> that is stable, like the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app, you may need to take manual action to keep automatic builds flowing every month.</p>
+<ul>
+<li>Put a calendar reminder to check every month on the 2nd day of the month (or later)<ul>
+<li>Check that <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> has a new build of the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> (or other) app</li>
+<li>If not, go to your <abbr title="contains project files and each file's revision history">repository</abbr> to see if the build action is disabled</li>
+</ul>
+</li>
+<li>If necessary, enable the build action at your <abbr title="contains project files and each file's revision history">repository</abbr> as shown in the graphic below and then launch a manual build</li>
+</ul>
+<p><img alt="fix a disabled build state" src="../img/build-disabled-fix.png" /></p>
+<p>This keeps the most recent version of your app available in <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> for you to install when you are ready. This manual enable step should be required no more frequently than every 60 days, however, best to make it a monthly habit to check.</p>
+<blockquote>
+<p>Builds in <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> are good for 90 days before they <a href="../../operation/features/notifications/#loop-app-expiration-notification" target="_blank">expire</a>.</p>
+</blockquote>
+<h2 id="what-is-automatic">What is Automatic<a class="headerlink" href="#what-is-automatic" title="Anchor link to this Header on this Page">&para;</a></h2>
 <p>These events are automatically scheduled:</p>
 <ul>
 <li>Once a week: Check for a new release of the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app:<ul>
@@ -3743,6 +3834,13 @@ <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Anchor l
 </li>
 <li>Once a month: Build the app and upload the fresh build to <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em></li>
 </ul>
+<div class="admonition important">
+<p class="admonition-title">You Get No Warning if Repository Build Action is Disabled</p>
+<p>These automatic actions happen on schedule, but if your build action is disabled, no build actually happens, no warning email is sent and a green checkmark (&#x2705;) appears beside a very short build action in which the actual build was skipped.</p>
+<ul>
+<li>Refer to <a href="#what-manual-action-is-required">What Manual Action is Required?</a></li>
+</ul>
+</div>
 <p>If you do not want this automatic schedule, you can modify it.</p>
 <p>Regardless of your choice, please <a href="../phone-install/#disable-automatic-install-from-testflight" target="_blank">Disable Automatic Installation from <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em></a>. You should be alert any time your <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app is updated. Check that all settings are maintained and pay attention to make sure the app behavior is nominal.</p>
 <p>You still need to <strong>take these actions</strong> to ensure a recent build of the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app is available in <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> for you to install on your phone when you choose:</p>
@@ -3759,6 +3857,13 @@ <h3 id="successful-weekly-action">Successful Weekly Action<a class="headerlink"
 <p>In that case, you should check your favorite information site to find out what the update was and then, when you are ready, install the update using the <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> app on your phone.</p>
 <h3 id="successful-monthly-action">Successful Monthly Action<a class="headerlink" href="#successful-monthly-action" title="Anchor link to this Header on this Page">&para;</a></h3>
 <p>On the first day of every month, you will see a successful <code>build action</code>. The purpose of this build is to provide a recent version of the app in <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> so you are never in a situation where you have no app on your phone.</p>
+<div class="admonition important">
+<p class="admonition-title">You Get No Warning if Repository Build Action is Disabled</p>
+<p>If your build action is disabled, no build actually happens, no warning email is sent and a green checkmark (&#x2705;) appears beside a very short build action in which the actual build was skipped.</p>
+<ul>
+<li>Refer to <a href="#what-manual-action-is-required">What Manual Action is Required?</a></li>
+</ul>
+</div>
 <p>You start getting <a href="../../operation/features/notifications/#loop-app-expiration-notification" target="_blank">Notifications</a> when there are fewer than 20 days until expiration. When you see the warning, install the newest build from your <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> app. You do not want to get the dreaded "<abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr> Beta is not available" message on your phone. (The warnings get very agressive when close to expiration.)</p>
 <h3 id="what-are-the-alive-branches">What are the <code>alive branches</code>?<a class="headerlink" href="#what-are-the-alive-branches" title="Anchor link to this Header on this Page">&para;</a></h3>
 <p>The automatic update and build feature is embedded in the build_loop.yml code and uses the <abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr> scheduling feature to trigger actions to run automatically.</p>

browser/bb-errors/index.html

@@ -1260,6 +1260,15 @@
     </span>
   </a>
 
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#manual-enable-for-build-action-may-be-required" class="md-nav__link">
+    <span class="md-ellipsis">
+      Manual Enable for Build Action May be Required
+    </span>
+  </a>
+  
 </li>
 
           <li class="md-nav__item">
@@ -4061,6 +4070,15 @@
     </span>
   </a>
 
+</li>
+        
+          <li class="md-nav__item">
+  <a href="#manual-enable-for-build-action-may-be-required" class="md-nav__link">
+    <span class="md-ellipsis">
+      Manual Enable for Build Action May be Required
+    </span>
+  </a>
+  
 </li>
 
           <li class="md-nav__item">
@@ -4546,6 +4564,10 @@ <h3 id="check-upstream-and-keep-alive-error"><code>Check Upstream and Keep Alive
 <p>On 21 April 2025, <em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> removed one of the third-party repositories that we used to keep automatic building going without action on your part. The <abbr title="contains project files and each file's revision history">repository</abbr> was removed because it was in violation of the <em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> terms of service. <em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> disables automatic actions for repositories that have been inactive (no commits added in 60 days). For stable apps, like the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app, this third-party <abbr title="contains project files and each file's revision history">repository</abbr> enabled a workaround to keep the builds happening.</p>
 <p>This affected all the Open-Source apps in our community - <abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr>, <abbr title="An app you can build to provide extra alarms and views of important information - can use Dexcom Share or `Nightscout` to include `Loop` information">LoopFollow</abbr>, <abbr title="An app you can build to provide remote commands to `Loop` using `Nightscout`">LoopCaregiver</abbr>, 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.</p>
 </div>
+<h3 id="manual-enable-for-build-action-may-be-required">Manual Enable for Build Action May be Required<a class="headerlink" href="#manual-enable-for-build-action-may-be-required" title="Anchor link to this Header on this Page">&para;</a></h3>
+<p>The automatic build actions continue to happen on schedule, but starting May 2025, you may find your build action disabled by <em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em>. (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 (&#x2705;) appears beside a very short build action in which the actual build was skipped.</p>
+<p>If necessary, enable the build action at your <abbr title="contains project files and each file's revision history">repository</abbr> as shown in the graphic below and then launch a manual build.</p>
+<p><img alt="fix a disabled build state" src="../img/build-disabled-fix.png" /></p>
 <h3 id="rebuild-create-certificates-error">Rebuild: Create Certificates Error<a class="headerlink" href="#rebuild-create-certificates-error" title="Anchor link to this Header on this Page">&para;</a></h3>
 <p>With <code>Loop 3.6.0</code>, these should be a thing of the past - but you must first manually update (sync) your <abbr title="contains project files and each file's revision history">repository</abbr> in order to get this feature added and you must do this new step <a href="../prepare-fork/#add-variable" target="_blank">Add Variable</a></p>
 <blockquote>

browser/bb-overview/index.html

@@ -3900,6 +3900,7 @@ <h3 id="mac-vs-browser">Mac vs Browser<a class="headerlink" href="#mac-vs-browse
 <li>Automatic Updates are loaded into <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em><ul>
 <li>With version 3.4 and newer, builds are automatically prepared at least once a month</li>
 <li>You choose when to install the new app from <abbr title="a method to distribute apps without direct connection">TestFlight</abbr> onto your phone</li>
+<li><strong>WARNING:</strong> starting May 2025, <a href="../automatic/#manual-action-for-automatic-build" target="_blank">Manual Action for Automatic Build</a> may be required - be sure to check monthly to see if you need to start a build manually</li>
 </ul>
 </li>
 <li>Manual Updates are easy<ul>

browser/bb-update/index.html

@@ -3925,6 +3925,7 @@ <h2 id="overview">Overview<a class="headerlink" href="#overview" title="Anchor l
 <p>Regardless of build method, this is an <strong>update</strong> and will install over your existing app; your <strong>settings are maintained including your current <abbr title="continuous glucose monitor, wearable medical device that measures and reports glucose in interstitial fluid">CGM</abbr> and Pump.</strong></p>
 </blockquote>
 <p><strong>For most, the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app is configured for automatic build, so you only need to come to this page if the automatic build failed.</strong></p>
+<p><strong>WARNING: starting May 2025, <a href="../automatic/#manual-action-for-automatic-build" target="_blank">Manual Action for Automatic Build</a> may be required - be sure to check monthly to see if you need to start a build manually.</strong></p>
 <details class="info" open="open">
 <summary>Time Estimate (click to open/close)</summary>
 <p>Manually update and build the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> App</p>
@@ -4093,19 +4094,20 @@ <h2 id="build-the-loop-app">Build the <em><abbr title="With a capital L, Loop is
 <p>This is Step 3 of 5 - this is always required.</p>
 </blockquote>
 <h4 id="build-the-app">Build the App<a class="headerlink" href="#build-the-app" title="Anchor link to this Header on this Page">&para;</a></h4>
-<p>Refer to graphic below as you follow the steps to build the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app.</p>
+<p>Refer to graphic below as you follow the steps to build the <em><abbr title="With a capital L, Loop is one of several do-it-yourself artifical pancreas systems">Loop</abbr></em> app. The numbers highlighted in the graphic correspond to numbers in parentheses in the bullet list below:</p>
 <ul>
-<li>Click on the <code>Actions</code> tab</li>
-<li>Select the <code>4. Build Loop</code> <abbr title="a set of instructions to GitHub to perform an action; the instruction files are found in the .github/workflows folder of the repository">workflow</abbr> on the left<ul>
+<li>(1) Click on the <code>Actions</code> tab</li>
+<li>(2) Select the <code>4. Build Loop</code> <abbr title="a set of instructions to GitHub to perform an action; the instruction files are found in the .github/workflows folder of the repository">workflow</abbr> on the left<ul>
 <li>If using a mobile browser, be sure to use landscape mode to more closely match how <em><abbr title="an online service for storing repositories, accessible from a browser">GitHub</abbr></em> looks on a computer.</li>
 </ul>
 </li>
-<li>Look on the right and click <code>Run workflow</code> to  see the dropdown</li>
-<li>Click on the green <code>Run workflow</code> button in the dropdown</li>
+<li>If you notice your build action is disabled, you must (3) click on <code>Enable workflow</code></li>
+<li>(4) Look on the right and click <code>Run workflow</code> to  see the dropdown</li>
+<li>(5) Click on the green <code>Run workflow</code> button in the dropdown</li>
 <li>Wait ~25 min for the build to complete successfully</li>
 <li>It is then processed by <em>Apple</em> and sent to <em><abbr title="a method to distribute apps without direct connection">TestFlight</abbr></em> (be patient)</li>
 </ul>
-<p align="center"><img alt="graphic indicating how to build again" src="../img/github-build-actions-build-again.svg" width="700" /></p>
+<p align="center"><img alt="graphic indicating how to build again" src="../img/build-disabled-fix.png" width="700" /></p>
 <h4 id="what-if-the-build-fails">What if the Build Fails<a class="headerlink" href="#what-if-the-build-fails" title="Anchor link to this Header on this Page">&para;</a></h4>
 <p>If a new release is announced at <a href="../../version/releases/#current-release" target="_blank">Current Release</a>, look to see if there are instructions about extra steps required with the release. </p>
 <blockquote>