Repository navigation
Align CI with flutter-geocoding and migrate Android builds - #63
Merged
Merged
Conversation
- Replace the per-package workflows with a single CI entry point that calls a reusable package workflow, as in flutter-geocoding. Packages are only checked when they changed, and ci-result is the single required check. - Use the flutter-geocoding version of the no-response workflow. - Add a dependabot configuration. - Raise the minimum Flutter version to 3.24, matching the Dart 3.5 SDK constraint, and bump the package versions. - Migrate the Android plugin and both example apps to the current Flutter Gradle setup (Kotlin DSL, AGP 9.1, Gradle 9.3, Java 17). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Brings the CI setup in line with flutter-geocoding and migrates the Android builds so they work on current Flutter stable (3.47).
CI
google_api_availability_ci.yaml. That workflow calls a reusablegoogle_api_availability_package.yamlfor each package. Each package runs format, analyze, its unit tests and, where it has one, an example build.dorny/paths-filterlimits each job to packages that changed. Starting the workflow by hand (workflow_dispatch) checks every package.ci-resultreports on every run, including when package jobs are skipped. Make it the only required status check in branch protection and remove the old per-package checks.mainand in geocoding.no-response.yaml..github/dependabot.ymlfor GitHub Actions, Gradle and pub, covering the packages and both example apps.SDK and versions
^3.5.0constraint.google_api_availabilityto 5.1.0,google_api_availability_androidto 1.2.0 andgoogle_api_availability_platform_interfaceto 1.1.0, with changelog entries. The platform interface's unreleased## nextentry is folded into 1.1.0.Android builds
minSdkstays at 16. Also removes thepackageattribute from the plugin manifest and the unused plugin Gradle wrapper.google_api_availability/exampleandgoogle_api_availability_android/example) from the Flutter 3.47 template: Kotlin DSL, Gradle 9.3.1, Java 17 and aMainActivity. Removes leftover v1-embedding activity references and Eclipse settings files.!in the Android test mock thatflutter analyzereported as a warning.No linked issue; this is maintenance.
Pre-launch Checklist
pubspec.yamlwith an appropriate new version according to the pub versioning philosophy, or this PR is does not need version changes.CHANGELOG.mdto add a description of the change.///).main.dart format .and committed any changes.flutter analyzeand fixed any errors.Verified locally on Flutter 3.47.9 / Dart 3.13.7: format, analyze and unit tests pass for all three packages, and
flutter build apk --releasesucceeds for both examples. The app-facing example builds againstgoogle_api_availability_android1.1.1 from pub.dev. Documentation is not affected.🤖 Generated with Claude Code