Merge pull request #343 from LoopKit/release/3.8.2

marionbarker · web-flow · commit cd643928a0ff · 2025-10-31T19:11:52.000-07:00
Release/3.8.2
diff --git a/.github/workflows/build_loop.yml b/.github/workflows/build_loop.yml
diff --git a/.github/workflows/validate_secrets.yml b/.github/workflows/validate_secrets.yml
@@ -5,7 +5,7 @@ on: [workflow_call, workflow_dispatch]
 jobs:
   validate-access-token:
     name: Access
-    runs-on: macos-15
+    runs-on: ubuntu-latest
     env:
       GH_PAT: ${{ secrets.GH_PAT }}
       GH_TOKEN: ${{ secrets.GH_PAT }}
@@ -71,13 +71,6 @@ jobs:
             exit 2
           fi
 
-  validate-match-secrets:
-    name: Match-Secrets
-    needs: validate-access-token
-    runs-on: macos-15
-    env:
-      GH_TOKEN: ${{ secrets.GH_PAT }}
-    steps:
       - name: Validate Match-Secrets
         run: |
           # Validate Match-Secrets
@@ -111,7 +104,7 @@ jobs:
 
   validate-fastlane-secrets:
     name: Fastlane
-    needs: [validate-access-token, validate-match-secrets]
+    needs: [validate-access-token]
     runs-on: macos-15
     env:
       GH_PAT: ${{ secrets.GH_PAT }}
diff --git a/.gitmodules b/.gitmodules
@@ -58,6 +58,3 @@
 [submodule "LibreTransmitter"]
 	path = LibreTransmitter
 	url = https://github.com/LoopKit/LibreTransmitter.git
-[submodule "DanaKit"]
-	path = DanaKit
-	url = https://github.com/loopandlearn/DanaKit
diff --git a/AmplitudeService b/AmplitudeService
@@ -1 +1 @@
-Subproject commit 219c0099ab8397c665f101124b97828dc159ee14
+Subproject commit 9a4aa7ff7aade2aca9d681b9122e15ad1cc90328
diff --git a/CGMBLEKit b/CGMBLEKit
@@ -1 +1 @@
-Subproject commit 34e15c4f34f1eeb04139d335c3fa9d93885dca8b
+Subproject commit 2e2ba3bdfdd90f4a00229f396b775b889da9876e
diff --git a/DanaKit b/DanaKit
diff --git a/G7SensorKit b/G7SensorKit
@@ -1 +1 @@
-Subproject commit 2ab622fffe4d815bdbb2e0c8bd6c4bc9e0bba52d
+Subproject commit 5139111ec6aa8a098163eab424a3a65bda09b86a
diff --git a/LibreTransmitter b/LibreTransmitter
@@ -1 +1 @@
-Subproject commit bd804da3b1b8ebf655693f90e9769845288c809a
+Subproject commit 25c31bae22082caaa6823179010129912d6c8f8f
diff --git a/LogglyService b/LogglyService
@@ -1 +1 @@
-Subproject commit 6ba482434343493a5f77ca28a7eeeafa8a250736
+Subproject commit c3504085286664f29b43b41ca9857a2dacf507b6
diff --git a/Loop b/Loop
@@ -1 +1 @@
-Subproject commit b81d866ecb246239c31a7dfb8fd3b16e547a7621
+Subproject commit c54fb10127f6365480d38258744d5d68918fae83
diff --git a/LoopKit b/LoopKit
@@ -1 +1 @@
-Subproject commit f8dafc7b6fd8c1dd6bc776854a5991a9b4e1d235
+Subproject commit 7237c73ce6f90475d356dffc6e155d7cc2b96240
diff --git a/LoopOnboarding b/LoopOnboarding
@@ -1 +1 @@
-Subproject commit fde5efb4c2cc38dd994a70300cde808a479a1640
+Subproject commit 60f57a77c9450df17c39f475542795e72f261136
diff --git a/LoopSupport b/LoopSupport
@@ -1 +1 @@
-Subproject commit 8d6a30c32457a5670b8c057eb08471640f812ee2
+Subproject commit 1370d8b3421765996e8e421be2ad94cb7f099af8
diff --git a/LoopWorkspace.xcworkspace/contents.xcworkspacedata b/LoopWorkspace.xcworkspace/contents.xcworkspacedata
diff --git a/LoopWorkspace.xcworkspace/xcshareddata/xcschemes/LoopWorkspace.xcscheme b/LoopWorkspace.xcworkspace/xcshareddata/xcschemes/LoopWorkspace.xcscheme
@@ -174,20 +174,6 @@
                ReferencedContainer = "container:OmniBLE/OmniBLE.xcodeproj">
             </BuildableReference>
          </BuildActionEntry>
-         <BuildActionEntry
-            buildForTesting = "YES"
-            buildForRunning = "YES"
-            buildForProfiling = "YES"
-            buildForArchiving = "YES"
-            buildForAnalyzing = "YES">
-            <BuildableReference
-               BuildableIdentifier = "primary"
-               BlueprintIdentifier = "3E6007862D0C5D0C00B186D1"
-               BuildableName = "DanaKitPlugin.loopplugin"
-               BlueprintName = "DanaKitPlugin"
-               ReferencedContainer = "container:DanaKit/DanaKit.xcodeproj">
-            </BuildableReference>
-         </BuildActionEntry>
          <BuildActionEntry
             buildForTesting = "YES"
             buildForRunning = "YES"
diff --git a/MinimedKit b/MinimedKit
@@ -1 +1 @@
-Subproject commit a8f58a993543a832400bd1427428f70300a5d4fa
+Subproject commit a1888623f398994e07ad970a0164be1117e9bec1
diff --git a/NightscoutRemoteCGM b/NightscoutRemoteCGM
@@ -1 +1 @@
-Subproject commit 46bb985f9504031e640489ece68ed14176c1670f
+Subproject commit acf26dbcfa34e041ecf6b798d80fc16689b52b6d
diff --git a/NightscoutService b/NightscoutService
@@ -1 +1 @@
-Subproject commit 1bd42382f4153bb15cc55228567cc8d453e05ca8
+Subproject commit a2723bbcb4014ac079c09c310d62484761aedf04
diff --git a/OmniBLE b/OmniBLE
@@ -1 +1 @@
-Subproject commit 331e08d0da50ba88bccf1bc088f7760dde6395dc
+Subproject commit b65dbfc2e34ea1f63c7c6d946aa828fcaba103af
diff --git a/OmniKit b/OmniKit
@@ -1 +1 @@
-Subproject commit cbf8dc00be1b21bed7c0872aee46a123b7954dc8
+Subproject commit 103fe3ca161ece2ff78e3c369149ff4561af669a
diff --git a/RileyLinkKit b/RileyLinkKit
@@ -1 +1 @@
-Subproject commit 7719fab42e476cf31a061d837c6ab1a521786f8e
+Subproject commit dc15267542d62f8ea3d869d5cd0bf7739bd9fe4d
diff --git a/Scripts/define_common.sh b/Scripts/define_common.sh
@@ -34,6 +34,7 @@ MESSAGE_FILE="xlate_message_file.txt"
 # matches lokalise order, en plus alphabetical order by language name in English
 LANGUAGES=(en \
     ar \
+    ce \
     zh-Hans \
     cs \
     da \
@@ -42,7 +43,8 @@ LANGUAGES=(en \
     fr \
     de \
     he \
-    hi ]
+    hi \
+    hu \
     it \
     ja \
     nb \
@@ -54,6 +56,7 @@ LANGUAGES=(en \
     es \
     sv \
     tr \
+    uk \
     vi \
 )
 
diff --git a/TidepoolService b/TidepoolService
@@ -1 +1 @@
-Subproject commit 1eb7ea11f63d1e5c34ad49c8718b9662b3fdb34f
+Subproject commit 84cab9b60e65b4aa814b0e12024a5e068ca65bfd
diff --git a/VersionOverride.xcconfig b/VersionOverride.xcconfig
@@ -8,5 +8,5 @@
 
 // Version [for DIY Loop]
 //   configure the version number in LoopWorkspace
-LOOP_MARKETING_VERSION = 3.8.1
+LOOP_MARKETING_VERSION = 3.8.2
 CURRENT_PROJECT_VERSION = 57
diff --git a/dexcom-share-client-swift b/dexcom-share-client-swift
@@ -1 +1 @@
-Subproject commit 2e9ebf07af058b6286f0e30e2051a62c9fe68a69
+Subproject commit 82a9179d444b3e79d5e9cfe99bbe7f298c4e8b40
diff --git a/fastlane/Fastfile b/fastlane/Fastfile
@@ -64,18 +64,6 @@ platform :ios do
       ]
     )
 
-    previous_build_number = latest_testflight_build_number(
-      app_identifier: "com.#{TEAMID}.loopkit.Loop",
-      api_key: api_key,
-    )
-
-    current_build_number = previous_build_number + 1
-
-    increment_build_number(
-      xcodeproj: "#{GITHUB_WORKSPACE}/Loop/Loop.xcodeproj",
-      build_number: current_build_number
-    )
-    
     mapping = Actions.lane_context[
       SharedValues::MATCH_PROVISIONING_PROFILE_MAPPING
     ]
diff --git a/fastlane/testflight.md b/fastlane/testflight.md
@@ -10,12 +10,10 @@ These instructions allow you to build your app without having access to a Mac.
 ## **Automatic Builds**
 > 
 > The browser build **defaults to** automatically updating and building a new version of Loop according to this schedule:
-> - automatically checks for updates weekly on Wednesdays and if updates are found, it will build a new version of the app
-> - automatically builds once a month regardless of whether there are updates on the first of the month
-> - with each scheduled run (weekly or monthly), a successful Build Loop log appears - if the time is very short, it did not need to build - only the long actions (>20 minutes) built a new Loop app
+> - automatically checks for updates weekly and if updates are found, it will build a new version of the app
+>   - even when there are no updates, it builds on the second Sunday of the month
+> - with each scheduled weekly run, a successful build log appears - if the time is very short, it did not need to build - only the long actions (>20 minutes) built a new app
 > 
-> It also creates an alive branch, if you don't already have one. See [Why do I have an alive branch?](#why-do-i-have-an-alive-branch).
->
 > The [**Optional**](#optional) section provides instructions to modify the default behavior if desired. 
 
 > **Repeat Builders**
@@ -191,7 +189,7 @@ You do not need to fill out the next form. That is for submitting to the app sto
 
 ## Create Building Certificates
 
-This step is no longer required. The Build Loop function now takes care of this for you. It does not hurt to run it but is not needed.
+This step is no longer required. The build action now takes care of this for you. It does not hurt to run it but is not needed.
 
 Once a year, you will get an email from Apple indicating your certificate will expire in 30 days. You can ignore that email. When it does expire, the next time an automatic or manual build happens, the expired certificate information will be removed (nuked) from your Match-Secrets repository and a new one created. This should happen without you needing to take any action.
 
@@ -212,13 +210,7 @@ Please refer to [LoopDocs: TestFlight Overview](https://loopkit.github.io/loopdo
 
 ## Automatic Build FAQs
 
-### Why do I have an `alive` branch?
-
-If a GitHub repository has no activity (no commits are made) in 60 days, then GitHub disables the ability to use automated actions for that repository. We need to take action more frequently than that or the automated build process won't work.
-
-The updated `build_loop.yml` file uses a special branch called `alive` and adds a dummy commit to the `alive` branch at regular intervals. This "trick" keeps the Actions enabled so the automated build works.
-
-The branch `alive` is created automatically for you. Do not delete or rename it! Do not modify `alive` yourself; it is not used for building the app.
+If a GitHub repository has no activity (no commits are made) in 60 days, then GitHub disables the ability to use automated actions for that repository. You may need to manually enable your build action and manually execute it when your fork becomes stale.
 
 ## OPTIONAL
 
@@ -248,18 +240,18 @@ You can modify the automation by creating and using some variables.
 
 To configure the automated build more granularly involves creating up to two environment variables: `SCHEDULED_BUILD` and/or `SCHEDULED_SYNC`. See [How to configure a variable](#how-to-configure-a-variable). 
 
-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**.
+Note that the weekly build 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: set `SCHEDULED_SYNC` to false and either do not create `SCHEDULED_BUILD` or set it to true
+* If you want to manually decide when to update your repository to the latest commit, but you want the monthly builds to continue: set `SCHEDULED_SYNC` to false and either do not create `SCHEDULED_BUILD` or set it to true
 * If you want to only build when an update has been found: set `SCHEDULED_BUILD` to false and either do not create `SCHEDULED_SYNC` or set it to true
     * **Warning**: if no updates to your default branch are detected within 90 days, your previous TestFlight build may expire requiring a manual build
 
 |`SCHEDULED_SYNC`|`SCHEDULED_BUILD`|Automatic Actions|
 |---|---|---|
-| `true` (or NA) | `true` (or NA) | keep-alive, weekly update check (auto update/build), monthly build with auto update|
-| `true` (or NA) | `false` | keep-alive, weekly update check with auto update, only builds if update detected|
-| `false` | `true` (or NA) | keep-alive, monthly build, no auto update |
-| `false` | `false` | no automatic activity, no keep-alive|
+| `true` (or NA) | `true` (or NA) | weekly update check (auto update/build), monthly build with auto update|
+| `true` (or NA) | `false` | weekly update check with auto update, only builds if update detected|
+| `false` | `true` (or NA) | monthly build, no auto update |
+| `false` | `false` | no automatic activity|
 
 ### How to configure a variable
 
@@ -280,12 +272,12 @@ Note that the weekly and monthly Build Loop actions will continue, but the actio
   
 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
+    - Run weekly every Sunday
+        - If updates are detected, it will update your repository and build
+        - If it is the second Sunday of the month, it will build even when no changes are detected
+- If you disable any automation (both variables set to `false`), no updates or building happens when the build action runs
+- If you disabled just scheduled synchronization (`SCHEDULED_SYNC` set to`false`), it will still build once a month, but no update will happen
+- If you disabled just scheduled build (`SCHEDULED_BUILD` set to`false`), it will run once weekly, to check for changes; if there are changes, it will update and build
 
 ## What if I build using more than one GitHub username
 
