-
Notifications
You must be signed in to change notification settings - Fork 7.8k
Update dev to 3.14.2 #453
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
marionbarker
wants to merge
6
commits into
dev
Choose a base branch
from
update_dev_to_3.14.2
base: dev
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Update dev to 3.14.2 #453
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
4ad21c1
Bump version to 3.14.2
marionbarker 488c57a
update Loop: warn if on dev, support OmnipodKit
marionbarker b27af62
update OmniBLE: fix identifier for 17e for Pod Keep Alive
marionbarker e18ef9a
update GitHub action to use Xcode 26.4
marionbarker 4cf9e34
update to fastlane 2.335.0
marionbarker a61dab4
add submodule OmnipodKit:
marionbarker File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,2 +1,2 @@ | ||
| source "https://rubygems.org" | ||
| gem "fastlane", "2.234.0" | ||
| gem "fastlane", "2.235.0" |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Submodule OmnipodKit
added at
c04c4d
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would prefer all the core device integrations for DIY Loop to remain in LoopKit. If there's some strong reason not to host it locally, let me know.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I don't think we should be punting the decision of which driver set to use (omnikit/omnible vs omnipodkit) to the user. That adds complexity for the user, for documentation, etc. When the new package is ready, it should be the integration for omnipod, and the old ones removed. I saw there is some automigration on the Loop side, which is nice.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just realized maybe my second point was already the plan. I think that's good; just would prefer that kind of unfinished business to stay on dev, and not be in a release.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding hosting of new managers - we have OmnipodKit pump manager plus others that we want to support in Loop. They are coming from other repositories:
e.g.
with at least one more to come that is private at this time.
We could set up forks within LoopKit for those repositories, and could set up scripts to keep them up to date with the upstream repositories.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Regarding the proposed configuration for dev and main 3.14.2, this is a temporary situation that is leading to having only OmnipodKit in feature branches, in the incoming tidepool-sync and in future releases.
This is why we need a main and dev version with all three pump managers before we make available a branch with only OmnipodKit.
We expect to move quickly to the next version where only OmnipodKit is provided, but we want to enable a wider pool of testers before forcing people to move to the new manager.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sounds like a good setup for dev, and not actually have a release, if we're not confident for release.