diff --git a/docs/faqs/app-translation.md b/docs/faqs/app-translation.md index ef23ec343b1..2d4b7fc5027 100644 --- a/docs/faqs/app-translation.md +++ b/docs/faqs/app-translation.md @@ -29,9 +29,11 @@ If a given phrase in the app does not have a translation string in what is calle For the *Loop* app and the submodules (Pumps, CGM and Services) associated with the *Loop* app, the [*lokalise*](https://app.lokalise.com/projects) website is used. You must be signed up with the *Loop* project to be able to see *Loop* translations at that site. -!!! note "Want to Sign Up to Translate?" +!!! note "Want to Translate?" To volunteer to translate, join [Loop zulipchat](https://loop.zulipchat.com/) and send a direct message to Marion Barker with your email address and the language(s) you can translate. + If you want translate one of the new CGM / Pump repositories: DanaKit, EversenseKit and MedtrumKit, indicate that as well. Those new repositories are handled using a [*crowdin* project](#crowdin-projects) for each repository. + ## Code Translation @@ -39,12 +41,37 @@ Localization (strings translated to the selected language in the app) makes use If you notice *Loop* app messages in English even though you selected a specific language, and you can help translate it, please volunteer. -Translations for Loop are performed by volunteers at [*lokalise*](https://app.lokalise.com/projects). +### Loop *lokalise* project + +Translations for most of the repositories used by Loop are performed by volunteers at [*lokalise*](https://app.lokalise.com/projects). + +Some newer CGM and Pump modules, currently found in feature branches, get their translations from *crowdin* instead of *lokalise*. + +* There was an early attempt to use both *lokalise* and *crowdin* but merging input from two sources was deemed impractical +* The DanaKit, MedtrumKit and EversenseKit translations are each handled by separate [*crowdin* projects](#crowdin-projects) + +### *crowdin* projects + +Some new pump and CGM modules are provided by developers associated with the *Trio* (*OpenAPS*) community. They have an established base of translators who are familiar with using *crowdin*. Translations for each of these new repositories is handled directly at the repository level. Loop translators who want to help with these repositories can just add that information to the request when they [volunteer to translate](#volunteer-to-translate). + +* [DanaKit crowdin](https://crowdin.com/project/danakit) +* [MedtrumKit crowdin](https://crowdin.com/project/medtrumkit) +* EversenseKit - not configured yet, coming soon -To volunteer, join [Loop zulipchat](https://loop.zulipchat.com/) and send a direct message to Marion Barker with your email address and the language(s) you can translate. You will get an invitation to join the project. You do not need to start a new project, start a free trial or sign up for anything special; just join the project you are invited to. +### Volunteer to Translate + +To volunteer, join [Loop zulipchat](https://loop.zulipchat.com/) and send a direct message to Marion Barker with your email address and the language(s) you can translate. Indicate whether you need access to the new repositories (*crowdin*) in addition to the Loop repositories. You will get an invitation to join the Loop *lokalise* project. You do not need to start a new *lokalise* project. Do not start a free *lokalise* trial or sign up for anything special; just join the project you are invited to. > If you are using the *Trio* or *iAPS* app instead of the *Loop* app, you can still assist with Pump, CGM and Tidepool module localization through *Loop* *lokalise*. Some repositories from *Loop* are used by [*Trio* and *iAPS*](#what-about-other-ios-apps). +Alternative contacts for addtion to *crowdin*: + +* Bastiaan Verhaar in zulipchat + * Bastiaan is known as `INeedSugar` in [Trio discord](https://discord.gg/FnwFEFUwXE) and [iAPS discord](https://discord.com/invite/ptkk2Y264Z) +* `lubor` in [iAPS discord](https://discord.com/invite/ptkk2Y264Z) + +## Lokalise Information + ### Initial Screen on *lokalise* When you log in to *lokalise*, you will see a screen similar to the screenshot below. Tap on the *Loop* icon, highlighted in the graphic with a red rectangle, to start translating. @@ -94,7 +121,7 @@ If a `key` does not have a translation in a given language, then when running th ### Select a Submodule -Suppose you know that you want to modify translations for a particular submodule (CGM, Pump or Service module). You can choose context in *lokalise*. +Suppose you know that you want to modify translations for a particular submodule (CGM, Pump or Service module). You can choose context in *lokalise*; or if it is one of the newer submodules, go directly to the *crowdin* project for that submodule. See [Submodule Table for Multiple Apps](#submodule-table-for-multiple-apps) for a detailed listing. * Tap on Filter * Tap on Context @@ -106,29 +133,11 @@ Suppose you know that you want to modify translations for a particular submodule The screenshot below is configured for someone translating simplified Chinese for the DanaKit pump. +**NOTE** The DanaKit keys are no longer visible in *lokalise*. They are being handled using [*crowdin*](#crowdin-projects). + ![choose a submodule for translation](img/lokalise-by-context-submodule-xcstrings.png){width="1024"} {align="center"} -#### Submodule Table for Multiple Apps - -These submodules are used by the *Loop*, *Trio* and *iAPS* apps. - -| Type |
Name | Files | -|:-:|:--|:--| -| CGM | `CGMBLEKit` | CGMBLEKit/CGMBLEKit/Localizable.xcstrings
CGMBLEKit/CGMBLEKitUI/Localizable.xcstrings | -| CGM | `G7SensorKit` | G7SensorKit/G7SensorKit/Localizable.xcstrings
G7SensorKit/G7SensorKitUI/Localizable.xcstrings | -| CGM | `LibreTransmitter` | LibreTransmitter/LibreTransmitter/Localizable.xcstrings
LibreTransmitter/LibreTransmitterUI/Localizable.xcstrings | -| CGM | `Dexcom Share` | dexcom-share-client-swift/ShareClient/Localizable.xcstrings
dexcom-share-client-swift/ShareClientUI/Localizable.xcstrings | -| CGM | `NightscoutRemoteCGM` | NightscoutRemoteCGM/NightscoutRemoteCGM/Localizable.xcstrings | -| Pump | `DanaKit` | DanaKit/Localization/Localizable.xcstrings | -| Pump | `MedtrumKit` | MedtrumKit/Localization/Localizable.xcstrings | -| Pump | `OmniBLE` | OmniBLE/Localizable.xcstrings
OmniBLE/OmniBLE/Localizable.xcstrings | -| Pump | `RileyLinkKit` | RileyLinkKit/RileyLink/Localizable.xcstrings
RileyLinkKit/RileyLink/LoopKit.xcstrings
RileyLinkKit/RileyLinkBLEKit/Localizable.xcstrings
RileyLinkKit/RileyLinkKitUI/Localizable.xcstrings | -| Pump | `MinimedKit` | MinimedKit/MinimedKit/Resources/Localizable.xcstrings
MinimedKit/MinimedKitUI/Resources/Localizable.xcstrings
MinimedKit/MinimedKitUI/Resources/mul.lproj/MinimedPumpManager.xcstrings| -| Pump | `OmniKit` | OmniKit/Localizable.xcstrings
OmniKit/OmniKit/Resources/Localizable.xcstrings
OmniKit/OmniKitUI/Resources/Localizable.xcstrings | -| Misc | `LoopKit` | LoopKit/LoopKit/Resources/Localizable.xcstrings
LoopKit/LoopKitUI/Resources/Localizable.xcstrings
LoopKit/LoopKitUI/Resources/mul.lproj/InsulinKit.xcstrings
LoopKit/LoopKitUI/Resources/mul.lproj/LegacyInsulinDeliveryTableViewController.xcstrings
LoopKit/MockKit/Resources/Localizable.xcstrings
LoopKit/MockKitUI/Resources/Localizable.xcstrings | -| Service | `TidepoolService` | TidepoolService/TidepoolServiceKit/Localizable.xcstrings
TidepoolService/TidepoolServiceKitUI/Localizable.xcstrings | - ### Matches Source Some of the String Catalogs have had the English version inserted in the translation field. This was done inadvertently. To find these instances in the language you are translating, set up a custom filter. @@ -173,12 +182,49 @@ The *Trio* and the *iAPS* apps use submodules for CGM, Pump and Service features The bottom line is -* Submodule translations are handled at [*lokalise*](https://app.lokalise.com/) +* Loop and older (pre 2025) submodule translations are handled at [*lokalise*](https://app.lokalise.com/) +* New submodules, DanaKit, EversenseKit, and MedtrumKit. are currently handled in [*crowdin* projects](#crowdin-projects) for the individual repositories * *Trio* translations are handled at [crowdin for *Trio*](https://crowdin.com/project/trio/invite/public?h=48e1a77abd1611860f475c1ce17540112591650&show_welcome) * *iAPS* translations are handled at [crowdin for *iAPS*](https://crowdin.com/project/iaps) You can use the *Trio* or *iAPS* discord server to volunteer to translate using *lokalise* by sending a direct message to Marion Barker if you are not a member of zulipchat. + +### Submodule Table for Multiple Apps + +These submodules are used by the *Loop*, *Trio* and *iAPS* apps and are handled by *lokalise*. + +| Type |
Name | Files | +|:-:|:--|:--| +| CGM | `CGMBLEKit` | CGMBLEKit/CGMBLEKit/Localizable.xcstrings
CGMBLEKit/CGMBLEKitUI/Localizable.xcstrings | +| CGM | `G7SensorKit` | G7SensorKit/G7SensorKit/Localizable.xcstrings
G7SensorKit/G7SensorKitUI/Localizable.xcstrings | +| CGM | `LibreTransmitter` | LibreTransmitter/LibreTransmitter/Localizable.xcstrings
LibreTransmitter/LibreTransmitterUI/Localizable.xcstrings | +| CGM | `Dexcom Share` | dexcom-share-client-swift/ShareClient/Localizable.xcstrings
dexcom-share-client-swift/ShareClientUI/Localizable.xcstrings | +| CGM | `NightscoutRemoteCGM` | NightscoutRemoteCGM/NightscoutRemoteCGM/Localizable.xcstrings | +| Pump | `OmniBLE` | OmniBLE/Localizable.xcstrings
OmniBLE/OmniBLE/Localizable.xcstrings | +| Pump | `RileyLinkKit` | RileyLinkKit/RileyLink/Localizable.xcstrings
RileyLinkKit/RileyLink/LoopKit.xcstrings
RileyLinkKit/RileyLinkBLEKit/Localizable.xcstrings
RileyLinkKit/RileyLinkKitUI/Localizable.xcstrings | +| Pump | `MinimedKit` | MinimedKit/MinimedKit/Resources/Localizable.xcstrings
MinimedKit/MinimedKitUI/Resources/Localizable.xcstrings
MinimedKit/MinimedKitUI/Resources/mul.lproj/MinimedPumpManager.xcstrings| +| Pump | `OmniKit` | OmniKit/Localizable.xcstrings
OmniKit/OmniKit/Resources/Localizable.xcstrings
OmniKit/OmniKitUI/Resources/Localizable.xcstrings | +| Misc | `LoopKit` | LoopKit/LoopKit/Resources/Localizable.xcstrings
LoopKit/LoopKitUI/Resources/Localizable.xcstrings
LoopKit/LoopKitUI/Resources/mul.lproj/InsulinKit.xcstrings
LoopKit/LoopKitUI/Resources/mul.lproj/LegacyInsulinDeliveryTableViewController.xcstrings
LoopKit/MockKit/Resources/Localizable.xcstrings
LoopKit/MockKitUI/Resources/Localizable.xcstrings | +| Service | `TidepoolService` | TidepoolService/TidepoolServiceKit/Localizable.xcstrings
TidepoolService/TidepoolServiceKitUI/Localizable.xcstrings | + +These submodules are used by the *Loop*, *Trio* and *iAPS* apps and are handled by *crowdin*. + +| Type |
Name | Files | +|:-:|:--|:--| +| Pump | `DanaKit` | see [DanaKit *crowdin*](https://crowdin.com/project/danakit) | +| Pump | `MedtrumKit` | see [MedtrumKit *crowdin*](https://crowdin.com/project/medtrumkit) | +| CGM | `EversenseKit` | crowdin project is not yet configured | + +The modules are specific to the particular app: + +| Type |
Name | Files | +|:-:|:--|:--| +| Loop | `Loop` | use [Loop *lokalise*](https://app.lokalise.com/projects) | +| Trio | `Trio` | use [Trio *crowdin*](https://crowdin.com/project/trio) | +| iAPS | `iAPS` | use [iAPS *crowdsin*](https://crowdin.com/project/iaps) | + + - - - ## Adding Languages diff --git a/docs/version/development.md b/docs/version/development.md index fe08eec26fb..6e29bc58a01 100644 --- a/docs/version/development.md +++ b/docs/version/development.md @@ -16,20 +16,19 @@ This section provides an overview of changes to `dev` compared to `Loop 3.8.x`. Please check the [development channel in zulipchat](https://loop.zulipchat.com/#narrow/channel/144182-development) for notifications when an update to the `dev` branch is expected so you will be prepared. Do this **before** you install a `dev` build from TestFlight. -With the `dev` branch, version 3.9.3, there are now differences between `dev` and `main`. In addition, there are some feature branches. +This section summarizes differences found in the`dev` branch, version 3.9.4, compared to `main`. In addition, there are some feature branches. -* Sometimes there is a work-in-progress branch, `update_dev_to_M.m.#` used to collect new items in preparation for the next `dev` branch. This allows people to test and comment on the updates. -* There are also feature branches for items like new pumps and new CGMs: - * The feature branches typically spin off of `dev`, but if a `updates_dev_to_ . . .` branch is in work, it is merged into the feature branches as items get included +??? tip "Updates in Progress (Click to open/close)" + * Sometimes there is a work-in-progress branch, `update_dev_to_M.m.#` used to collect new items in preparation for the next `dev` branch. This allows people to test and comment on the updates before they land in the `dev` branch. + * There are also feature branches for items like new pumps and new CGMs: + * The feature branches typically spin off of `dev`, but if a `updates_dev_to_ . . .` branch is in work, it is merged into the feature branches as items get included -|
branch | version # | last updated | comments | +|
branch | version # |
last updated | comments | |:--|:--|:--|:--| -| main | 3.8.2 | 31 October 2025 | release | -| dev | 3.9.3 | 22 November 2025 | Adds Live Activity, Browser Build improvement, translation and other updates
See [v3.9.3 `dev`](#v393-dev) | -| update_dev_to_3.9.4 | 3.9.4 | 24 December 2025 | Work in progress for next dev branch
[Commits Page](https://github.com/LoopKit/LoopWorkspace/commits/update_dev_to_3.9.4/) | -| [feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)
- SHA `9bc2bae` | 3.9.4 | 24 December 2025 | - uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 phones with InPlay BLE (-Atlas) DASH pods
- SHA for OmniBLE is `e10964be`
**Please read [OmniBLE Keep-Alive](#omnible-keep-alive)** | -| [feat/dev-dana-medtrum](#feature-branch-medtrum-and-dana-support)
- SHA `c775906`| 3.9.4 | 24 December 2025 | - adds experimental support for Dana and Medtrum pumps
- this branch is ready for expert testers to evaluate and report back
- SHA for DanaKit is `92d2cd7`
- SHA for MedtrumKit is ` db71473` | -| release/3.8.1 | 3.8.1 | will be removed soon | - copy of the main release at version 3.8.1 that included Dana support
- please build the feat/dev-dana-medtrum branch instead and test it
- this branch was a stop-gap measure to support people already using Dana with v3.8.1 who understood how to manage the issues with that version; it will be deleted soon
- SHA for DanaKit is `3e606b8` | +| main | 3.8.2 | 31 Oct 2025
07 Dec 2025 | release
Browser Build hot-fix same version | +| dev | 3.9.4 | 31 Dec 2025 | v3.9.3 Add Live Activity
v3.9.4 Add Omnipod updates, Purge excessive log file storage, Add CAGE and IAGE to Minimed UI screen, Improve Browser Build, Update to fastlane 2.230.0, Update translations
See [v3.9.4 `dev`](#v394-dev) | +| [feat/pod-keep-alive](#feature-branch-pod-keep-alive-feature)
- SHA `5eba785` | 3.9.4 | 31 Dec 2025 | - uses the OmniBLE pod-keep-alive branch to support users of iPhone 16 phones with InPlay BLE (-Atlas) DASH pods
- SHA for OmniBLE is `41dd40e`
**Please read [Feature Branch: Pod Keep Alive Feature](#feature-branch-pod-keep-alive-feature)** | +| [feat/dev-dana-medtrum](#feature-branch-medtrum-and-dana-support)
- SHA `84f32bf` | 3.9.4 | 31 Dec 2025 | - adds experimental support for Dana and Medtrum pumps
- this branch is ready for expert testers to evaluate and report back
- SHA for DanaKit is `f01a75a9`
- SHA for MedtrumKit is ` db71473` | ??? question "What is SHA? (Click to Open/Close)" SHA-1 means Secure Hash Algorithm 1. This is used to generate an alphanumeric code to identify which version of a repository is used. @@ -38,6 +37,70 @@ With the `dev` branch, version 3.9.3, there are now differences between `dev` an The SHA-1 20-character value is abbreviated as SHA and typically only the first 7 or 8 characters are presented to identify the commit for a particular repository. + +### v3.9.4 `dev` + +#### Minimum Requirements + +!!! important "Minimum Requirements" + **Although the build will succeed for iOS 15 and 16 devices, not all features are supported** + + * Please update your phone hardware to something that supports iOS 18 or iOS 26 + * Be sure your build is 3.8.2 or newer before updating your phone to iOS 26 + * See [Compatible Device](../build/phone.md#compatible-device){: target="_blank" } + + For iOS 16 and older not all features for Live Activity / Dynamic Island / CarPlay features are supported; and for iOS 15 even more features are not supported, including some translations. + +#### Differences between `main` and `dev` + +The `dev` branch labeled v3.9.4 includes these updates with respect to the `main` branch + +* Live Activity, Dynamic Island and CarPlay: see [Live Activities](#live-activities) + +* OmniBLE and OmniKit: + * handle cases where a pod was discarded rather than deactivated more accurately + * ensure completion for acknowledgeAlert +* LibreTransmitter: reduce the log size +* LoopKit: automatically purge log files to prevent excessive on-phone storage +* MinimedKit: add CAGE and IAGE to pump settings view +* New translations +* Use fastlane 2.230.0 (for browser build) + +#### Live Activities + +Live Activity was added to Loop with this [Loop PR 2919](https://github.com/LoopKit/Loop/pull/2191#issuecomment-3565473537). Many people have been using this as a customization. If you used the customization - you need to stop selecting `live_activity` as a customization or your build will fail. + +* The configuration for the Live Activity widget on the lock screen is found under Loop, Settings, Notifications, Live Activity +* You must also enable Live Activity under iPhone settings, Loop, tap on Live Activites and enable Allow Live Activites and More Frequent Update + +##### Requirements for Live Activities + +* The dynamic island is only available for iPhone versions 14 pro and newer; but Live Activity on the Lock Screen is supported for older phones running iOS 16 or newer +* iOS 18 and watchOS 10 or newer are required for Live Activity to appear in the Smart Stack on the Apple Watch +* iOS 26 or newer is required to have Live Activity appear in the CarPlay view + + + +### PR Links for `dev` Updates + +The details of the additions to the `dev` branch for v3.9.4 are found in LoopWorkspace Pull Request 367: + +* [Update dev to 3.9.4](https://github.com/LoopKit/LoopWorkspace/pull/367) + +The details of the additions to the `dev` branch for v3.9.3 are found in LoopWorkspace Pull Request 358: + +* [Update dev to 3.9.3](https://github.com/LoopKit/LoopWorkspace/pull/358) + + +#### Mac-Xcode Builders + +One change with v3.9.3 and newer is to modify the Build Order selected in Xcode from the deprecated `Manual Order` to the preferred `Dependency Order`. + +* If you start with a fresh download - this will not affect you +* If you update an existing clone on your computer with the `git pull --recurse` command, you will need to perform a `Product: Clean Build Folder` in Xcode, close the workspace in Xcode and reopen it + * If there are still build errors, then quit out of Xcode, issue the following command and try again + * `rm -rf ~/Library/Developer/Xcode/DerivedData` + ### How to Build Feature Branches For full instructions on building different branches, review these pages: @@ -62,7 +125,20 @@ For Mac Xcode build, the lines you need to copy and paste into a Terminal window - feat/dev-dana-medtrum ``` -### OmniBLE Keep-Alive +### Version Number Plan + +Please see [`Loop` Version Numbering](releases.md#loop-version-numbering) for the current method for version numbering for the `main` and `dev` branches. + +The idea of having a feature branch is not new for the *Loop* app but hasn't been used for a few years. At this point, we have two feature branches. + +Moving forward, the version number in the feature branch will match the `dev` branch version number, or in some cases, a work-in-progress update to the `dev` branch which uses the naming convention `update_dev_to_M.m.#`. + +* In other words, the feature branch is up to date with other changes to `dev` or `update_dev_to_M.m.#` with the added support for the specific feature +* Each feature has an associated repository that contains the feature + * When updates to the feature are added, the SHA for the feature branch and the SHA for the submodule(s) which support that feature will be reported in the table above and can be found by examining the LoopWorkspace repository for that feature branch + + +### Feature Branch: Pod Keep Alive Feature The experimental `pod-keep-alive` branch has a new "Pod Keep Alive" option at the bottom of the "Omnipod DASH" screen. This is intended to assist users who have both an [iPhone 16 and DASH pods with a InPlay BLE (Atlas) board](../faqs/omnipod-faqs.md#iphone-16-and-atlas-or-inplay-dash-pods){: target="_blank" }. No action is taken automatically unless both these cases are detected to be true. @@ -132,60 +208,6 @@ While RileyLink is selected, the app is triggered by the RileyLink one minute he > If the phone moves out of RileyLink range, then the app is not triggered by the RileyLink heartbeat and the pod disconnects from BLE at the 3 minute cadence. With iPhone 16 it might take several seconds to minutes before the app reconnects to the pod once it is back in range. This can cause disruptions until the reconnect happens. -### Version Number Plan - -Please see [`Loop` Version Numbering](releases.md#loop-version-numbering) for the current method for version numbering for the `main` and `dev` branches. - -The idea of having a feature branch is not new for the *Loop* app but hasn't been used for a few years. At this point, we have two feature branches. - -Moving forward, the version number in the feature branch will match the `dev` branch version number. - -* In other words, a diff between `dev` and the feature branch is just the updates added to support the feature compared to that version of `dev` -* As appropriate, `dev` will be merged into the feature branch and at that time, the version number for the feature branch will also be bumped -* Updates to the feature branch to support the feature will not be updated with a new version number associated with the features - * When updates for the feature are added, the SHA for that submodule will be reported in the table above and can be found by examining the LoopWorkspace repository for that feature branch - -### v3.9.3 `dev` - -The details of the additions to the `dev` branch for v3.9.3 are found in LoopWorkspace Pull Request 358: - -* [Update dev to 3.9.3](https://github.com/LoopKit/LoopWorkspace/pull/358) - -!!! important "New Minimum Requirements" - **The minimum iOS required to build this version is iOS 16; but not all features are supported by iOS 16 - specifically the Live Activity / Dynamic Island / CarPlay features** - - * Correction, you can still build onto an iOS 15 phone with this version, but because the use of String Catalogs for languages don't work well for iOS 15 and Live Activity is not supported, expect the next dev version will force a minimum iOS 16 for building - - **Live Activity, Dynamic Island and CarPlay** - - * The dynamic island is only available for iPhone versions 14 pro and newer; but Live Activity on the Lock Screen is supported for older phones running iOS 16 or newer - * iOS 18 and watchOS 10 or newer are required for Live Activity to appear in the Smart Stack on the Apple Watch - * iOS 26 or newer is required to have Live Activity appear in the CarPlay view - - -#### Live Activities - -This update adds Live Activity to Loop with [Loop PR 2919](https://github.com/LoopKit/Loop/pull/2191#issuecomment-3565473537). Many people have been using this as a customization. If you used the customization - you need to stop selecting `live_activity` as a customization or your build will fail. - -* The configuration for the Live Activity widget on the lock screen is found under Loop, Settings, Notifications, Live Activity -* You must also enable Live Activity under iPhone settings, Loop, tap on Live Activites and enable Allow Live Activites and More Frequent Update - -#### Mac-Xcode Builders - -One change with this PR is to modify the Build Order selected in Xcode from the deprecated `Manual Order` to the preferred `Dependency Order`. - -* If you start with a fresh download - this will not affect you -* If you update an existing clone on your computer with the `git pull --recurse` command, you will need to perform a `Product: Clean Build Folder` in Xcode, close the workspace in Xcode and reopen it - * If there are still build errors, then quit out of Xcode, issue the following command and try again - * `rm -rf ~/Library/Developer/Xcode/DerivedData` - -### Feature Branch: Pod Keep Alive Feature - -For more information about using the `feat/pod-keep-alive` branch with an iPhone 16 and InPlay BLE DASH pods, please refer to the README file for the OmniBLE `pod-keep-alive` branch: - -* [Workaround for InPlay Pods](https://github.com/LoopKit/OmniBLE/tree/8c4740468949cf6ca787e232f885a535b2bb3e8f?tab=readme-ov-file#omnible) - - ### Feature Branch: Medtrum and Dana Support **Updates are believed to have fixed the active insulin issues reported for both Dana and Medtrum, but this should be tested by experts to confirm pumps are working well with Loop.** @@ -193,9 +215,10 @@ For more information about using the `feat/pod-keep-alive` branch with an iPhone !!! important "Experts Only" Please only use the `feat/dev-dana-medtrum` branch if you are prepared to follow along in zulipchat and are willing to test an experimental branch to help test and resolve issues. - * Please ensure you have the latest version of this branch: + * Please ensure you have the latest version of this branch by synching before you build: * `feat/dev-dana-medtrum` - * SHA `de1109f` + * Mac-Xcode: type `git pull --recurse` to update an existing clone or download a fresh copy + * Browser Build, the Build Loop action, with the `feat/dev-dana-medtrum` branch selected should automatically sync your fork for you ## Older updates diff --git a/docs/version/releases.md b/docs/version/releases.md index 46df8520f43..9d287dc66a0 100644 --- a/docs/version/releases.md +++ b/docs/version/releases.md @@ -545,7 +545,8 @@ For example: * `Loop v3.6.1`, `Loop v3.6.2`, `Loop v3.6.3` and `Loop v3.6.4` were updates without major changes to the features of `Loop v3.6` * `Loop v3.7.7` was the development version before `Loop v3.8.0` was released * `Loop v3.8.0` was the next minor release - * `Loop v3.9.0` is the current development version, see [Updates in dev](development.md#updates-in-dev) for functional differences, if any, between `main` and `dev` + * `Loop v3.8.1`, `Loop v3.8.2` were hotfixes to handle iOS 26 issues without major changes to the features of `Loop v3.8` with the important exception that DanaKit support was spun off to a feature branch with v3.8.2 + * `Loop v3.9.x` is the current development version, see [Updates in dev](development.md#updates-in-dev) for functional differences, if any, between `main` and `dev` - - -