Upgrade minSdkVersion in app level build.gradle for all_packages test

[gmackall]

I am about to land a migrator in flutter/flutter which will upgrade minSdkVersions in app-level build.gradle files to 19, but want to make these changes to the packages repo ahead of time. It ended up only mattering in one place though, from what I can tell.

Migrator PR here: flutter/flutter#129729

Part of flutter/flutter#82000

Pre-launch Checklist

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• I read the Tree Hygiene wiki page, which explains my responsibilities.
• I read and followed the relevant style guides and ran the auto-formatter. (Unlike the flutter/flutter repo, the flutter/packages repo does use dart format.)
• I signed the CLA.
• The title of the PR starts with the name of the package surrounded by square brackets, e.g. [shared_preferences]
• I listed at least one issue that this PR fixes in the description above.
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy, or this PR is exempt from version changes.
• I updated CHANGELOG.md to add a description of the change, following repository CHANGELOG style.
• I updated/added relevant documentation (doc comments with ///).
• I added new tests to check the change I am making, or this PR is test-exempt.
• All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

[stuartmorgan-g]

I am about to land a migrator in flutter/flutter which will upgrade minSdkVersions in app-level build.gradle files to 19, but want to make these changes to the packages repo ahead of time.

We support stable, which still supports pre-19; wouldn't it make more sense to wait until stable is 19+, and then update packages? That's how we did the last iOS support drop.

[gmackall]

I am about to land a migrator in flutter/flutter which will upgrade minSdkVersions in app-level build.gradle files to 19, but want to make these changes to the packages repo ahead of time.

We support stable, which still supports pre-19; wouldn't it make more sense to wait until stable is 19+, and then update packages? That's how we did the last iOS support drop.

Thanks for pointing this out, yes that does make more sense. My mistake!