Skip to content

Commit 705e338

Browse files
committed
add information about disabled builds
1 parent b375155 commit 705e338

File tree

2 files changed

+27
-5
lines changed

2 files changed

+27
-5
lines changed

docs/browser/automatic.md

Lines changed: 13 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -12,11 +12,18 @@ The instructions provided for building with a browser include settings to automa
1212
* **inactive** means stable code (no new commit within the last 60 days)
1313
* **disables actions** means the Build Action shows up as disabled
1414

15+
!!! warning "Browser Build Disabled"
16+
We do not know why, but GitHub is disabling the Build Loop Action for LoopWorkspace even though the repository is not stale.
17+
18+
* We think it is associated with running too many builds at a busy time that requested too many runners (virtual computers)
19+
* The redesigned build action for v3.8.2 should alleviate this
20+
* We also plan to reach out to GitHub after people have transitioned to the v3.8.2 build schedule
21+
1522
### What Manual Action is Required?
1623

17-
For any repository that is stable, like the *Loop* app, you may need to take manual action to keep automatic builds flowing every month.
24+
For any repository that shows the build action disabled, you should enable the action and do a manual build.
1825

19-
* Put a calendar reminder to check every month on the 2nd day of the month (or later)
26+
* Put a calendar reminder to check every month on the 15th day of the month (or later)
2027
* Check that *TestFlight* has a new build of the *Loop* (or other) app
2128
* If not, go to your repository to see if the build action is disabled
2229
* 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
2734

2835
> Builds in *TestFlight* are good for 90 days before they [expire](../operation/features/notifications.md#loop-app-expiration-notification){: target="_blank" }.
2936
37+
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.
38+
39+
* Head over to [Errors with Browser](bb-errors.md){: target="_blank" }
40+
3041
## What is Automatic
3142

3243
These events are automatically scheduled:

docs/version/releases.md

Lines changed: 14 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -10,7 +10,7 @@ For information about version 2 releases and compatibility between version 2 and
1010

1111
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).
1212

13-
> When main was 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.
13+
> 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.
1414
1515
> See [Updates in `dev`](development.md#updates-in-dev){: target="_blank" } for a summary of difference, if any, between `main` and `dev`.
1616
@@ -43,7 +43,18 @@ Releases from `Loop v3.4.4` and older are reported at [*GitHub*&nbsp;_<span tran
4343

4444
### Loop v3.8.2
4545

46-
[*Loop* v3.8.2](https://github.com/LoopKit/LoopWorkspace/releases/tag/v3.8.2) was released on TBD October 2025.
46+
!!! warning "Browser Build Disabled"
47+
We do not know why, but GitHub is disabling the Build Loop Action for LoopWorkspace.
48+
49+
* We think it is associated with running too many builds at a busy time that requested too many runners (virtual computers)
50+
* The redesigned build action for v3.8.2 should alleviate this
51+
* We also plan to reach out to GitHub after people have transitioned to the v3.8.2 build schedule
52+
53+
> Please follow these steps to build manually and then once that build completes, enable the build action again.
54+
55+
> * [What Manual Action is Required?](../browser/automatic.md#what-manual-action-is-required){: target="_blank" }
56+
57+
[*Loop* v3.8.2](https://github.com/LoopKit/LoopWorkspace/releases/tag/v3.8.2) was released on 31 October 2025.
4758

4859
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.
4960

@@ -55,7 +66,7 @@ This version updates a few iOS 26 interface issues, moves support for Dana pumps
5566
* [Remove DanaKit](#why-was-danakit-support-changed) support from `main` and `dev` branches of the *Loop* app
5667
* Update some translations
5768

58-
> When main was 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.
69+
> 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.
5970
6071
#### Why was DanaKit Support Changed
6172

0 commit comments

Comments
 (0)