Update to macos 15, fastlane 2.225.0 for tidepool-merge #220
Conversation
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
Contributor
Author
|
I installed the TestFlight build on a test phone and confirmed that the expiration date is not included. |
marionbarker
changed the title
Contributor
Author
|
I converted to a draft until the work on dev is finished. This will be updated or replaced at that time. |
Contributor
Author
|
Going to close this because we want a new with more up to date settings. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This fixes two items that stopped working for building with GitHub on or about Nov 4, 2024.
Here's the link for the full details about why the runner had to be changed to macos-15:
The update the Fastlane 2.225.0 fixed a problem explained in more detail in this zulipchat post
I tested a Browser Build with
tidepool-mergecommit 17aa656 and it failed, failed build log.I tested with the update in this PR and the Browser Build succeeded: successful log