This pull request was opened against a branch other than master. Since Flutter pull requests should not normally be opened against branches other than master, I have changed the base to master. If this was intended, you may modify the base back to stable. See the Release Process for information about how other branches get updated.

Reviewers: Use caution before merging pull requests to branches other than master, unless this is an intentional hotfix/cherrypick.

Shouldn't the pubspec checksum be updated when changing versions? We might want to hold off on these until next week.

the merge target should be a release-candidate branch, also, not stable. I'm guessing the branch should be: flutter-3.16-candidate.0? Per https://github.com/flutter/flutter/blob/stable/bin/internal/release-candidate-branch.version

Shouldn't the pubspec checksum be updated when changing versions? We might want to hold off on these until next week.

How do I update the pubspec checksum?

Shouldn't the pubspec checksum be updated when changing versions? We might want to hold off on these until next week.

How do I update the pubspec checksum?

Probably the best way to do so for release cherry picks would be to use:

flutter update-packages --cherry-pick-package=dwds --cherry-pick-version='21.0.0+1'

This will ensure ONLY dwds is changed, and that the checksum is written.

Thanks! Updated the checksum