Repository navigation
material_color_utilities is pinned as a dependency in package:flutter #185017
Description
We are waiting to clarify the status here before unpinning.
Most likely this will go away when package:material is external?
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
dkwingsmt commentedon Apr 15, 2026
cc @justinmc
Marking it as P1 because it is related to decoupling.
justinmc commentedon Apr 15, 2026
@sigurdm Yes it looks like material_color_utilities is only used in material/color_scheme.dart, which is moving out to the material_ui package. However keep in mind that this code won't be deleted for another year, only deprecated for now, so the dependency in pubspec.yaml will have to remain for quite some time.
sigurdm commentedon Apr 17, 2026
Right, that actually makes the unpinning important, otherwise using package:flutter from the sdk will block you from using newer versions of package:material.
But I think I'll leave it to the Flutter team to figure out how they'll do that best.
justinmc commentedon Jul 14, 2026
@QuncCccccc do you have any idea why material_color_scheme was pinned? I see it's only used in color_scheme.dart.
My thinking is that we should just unpin it and make it a caret dependency in material_ui. I'm thinking after 1.0.0, though it shouldn't cause any migration trouble to do it pre-1.0.0.
stuartmorgan-g commentedon Jul 14, 2026
Until recently, everything in flutter/flutter was pinned. Unpinning is a recent change, and I believe this package was left out during the first iteration only because it was potentially going to be mooted for flutter/flutter by the move to packages.
You won't be able to publish from flutter/packages with a pinned runtime dependency unless we make special CI changes to ignore the warning that
pubwill give when you try. I would not want to do that without an extremely compelling reason.Since the source repo for the package is an Alphabet repo, I would expect that this would fall under our (flutter/packages) criteria for unpinned deps.
justinmc commentedon Jul 16, 2026
Sounds like we should unpin it now then: flutter/packages#12225
[material_ui] Unpin material_color_utilities (flutter#12225)
[material_ui] Unpin material_color_utilities (flutter#12225)
github-actions commentedon Aug 3, 2026
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.