Skip to content
Permalink

Comparing changes

Choose two branches to see what’s changed or to start a new pull request. If you need to, you can also or learn more about diff comparisons.

Open a pull request

Create a new pull request by comparing changes across two branches. If you need to, you can also . Learn more about diff comparisons here.
base repository: flutter/packages
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: 4b424d786b09
Choose a base ref
...
head repository: flutter/packages
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: 10cbdc57b0ce
Choose a head ref
  • 3 commits
  • 40 files changed
  • 2 contributors

Commits on May 27, 2026

  1. [google_maps_flutter] Federate READMEs (#11790) 

    Moves the platform-specific setup logic and discussion from the main README to the platform READMEs, per our current best practice.

As part of the move, I simplified the discussion of the iOS implementation package choice somewhat, since I realized there was too much explanation of why things are the way they are, rather than on the steps a client should take.

There's a repeated example code block across the iOS packages now, but I think duplicating that is much better than being inconsistent about where setup info is (or worse, pointing them to one implementation package that's not the same as the one they are using).

Part of flutter/flutter#182772

## Pre-Review Checklist

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
    @stuartmorgan-g
    stuartmorgan-g authored May 27, 2026
    Configuration menu
    Copy the full SHA
    b74a269 View commit details
    Browse the repository at this point in the history

  2. [tool] Add LICENSE file (#11796) 

    When restoring the repo tools to a publishable state, I forgot that we need a package-level LICENSE file. This adds the standard repo LICENSE to pass `publish --dry-run`.
    @stuartmorgan-g
    stuartmorgan-g authored May 27, 2026
    Configuration menu
    Copy the full SHA
    c23d051 View commit details
    Browse the repository at this point in the history

  3. [in_app_purchase_android] Update Play Billing library to 8.0.0 (#10816) 

    Updates Play Billing Library to the latest version 8.0.0. Exposes new APIs as per [release notes](https://developer.android.com/google/play/billing/release-notes#8-0-0):
*   Adds new `subResponseCode` to `BillingResultWrapper` and `PlatformBillingResult`.
*   Adds `unfetchedProductList` to `ProductDetailsResponseWrapper` and `PlatformProductDetailsResponse` to expose products that could not be retrieved.
*   Adds Dart representation of `UnfetchedProductWrapper`.
*   Adds `oneTimePurchaseOfferDetailsList` to `ProductDetailsWrapper` to support multiple one-time purchase offers.
*   Removes the deprecated `queryPurchaseHistory` method on `BillingClientWrapper` as it has been removed from the native library (breaking change). Users should use `restorePurchases` (which uses `queryPurchasesAsync` instead.

This PR introduces breaking changes in `in_app_purchase_android`, but does not introduce any breaking changes on the platform interface level.

Fixes flutter/flutter#171523

## Pre-Review Checklist

**Note**: The Flutter team is currently trialing the use of [Gemini Code Assist for GitHub](https://developers.google.com/gemini-code-assist/docs/review-github-code). Comments from the `gemini-code-assist` bot should not be taken as authoritative feedback from the Flutter team. If you find its comments useful you can update your code accordingly, but if you are unsure or disagree with the feedback, please feel free to wait for a Flutter team member's review for guidance on which automated comments should be addressed.

[^1]: Regular contributors who have demonstrated familiarity with the repository guidelines only need to comment if the PR is not auto-exempted by repo tooling.
    @jmagman
    jmagman authored May 27, 2026
    Configuration menu
    Copy the full SHA
    10cbdc5 View commit details
    Browse the repository at this point in the history
Loading