Skip to content

Conversation

@marionbarker
Copy link
Contributor

Purpose

  1. Bring the fastlane version up to 2.231.0
  2. Add a commit so the repository does not become stale

Details

The preparation for fastlane version 2.231.0 was completed for LoopFollow. This PR brings the Gemfile and Gemfile.lock into alignment with LoopFollow (see LoopFollow PR 500).

  • Although fastlane 2.231.1 has been released, it has not yet been tested for OS-AID apps and that update will be used later to prevent this repository from becoming stale.

As of 26 Jan 2026, it has been 48 days since the last commit. When the days since last commit reaches 60, then GitHub will disable all automatic actions for downstream forks that have not added a commit in 60 days. Once GitHub disables a build action, manual steps are required by the owners of the downstream forks to restore automatic building.

Automatic builds happen on Sunday when a new commit was added to the upstream repository or on the 2nd Sunday of each month regardless of the commit state of the upstream repository.

Test

This version of Gemfile and Gemfile.lock was thoroughly tested before merging into LoopFollow.

Spot check this PR for LoopCaregiver.

Use https://github.com/docs-test/LoopCaregiver/actions for testing

  • push the fastlane_2.231.0 to docs test and make that branch the default
  • ✅ Ensure Add Identifiers works
    • delete the App Group from one identifier
    • run Add Identifiers
    • add back the LoopCaregiver app group
  • ✅ Ensure Build LoopCaregiver works

@gestrich gestrich merged commit 26068aa into LoopKit:dev Jan 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants