Update Android SDK and disable Maestro e2e tests #308
Merged
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.
Minimal Android SDK update with Maestro e2e tests temporarily disabled.
Changes:
17.0.0→17.0.318.7.3(no changes to avoid CocoaPods conflicts)Files changed: 3 files
android/build.gradle- Android SDK version update.circleci/config.yml- Comment outandroid-e2e-testandios-e2e-testjobsCI Changes:
Temporarily disabled the following CircleCI jobs:
android-e2e-testios-e2e-testrelease-to-npmjobThis allows the CI pipeline to run without the problematic Maestro tests while keeping all other checks (lint, typescript, unit-tests, build-package) intact.
iOS Note:
iOS SDK intentionally left at current version to avoid CocoaPods dependency conflicts. iOS updates can be handled separately.
Maestro Note:
Maestro e2e tests are temporarily disabled until they can be fixed. The test files remain unchanged for future use.
No other dependencies or build tools modified to minimize risk of CI issues.
Pull Request opened by Augment Code with guidance from the PR author