autosubmit label was removed for flutter/flutter/170000, because - The status or check suite Windows framework_tests_libraries has failed. Please fix the issues identified (or deflake) before re-applying this label.

I almost want to make a branch on material at the last merge and apply the fixes so we don't have to throw the baby out with the bath water.

Will ponder...

This pull request has been changed to a draft. The currently pending flutter-gold status will not be able to resolve until a new commit is pushed or the change is marked ready for review again.

For more guidance, visit Writing a golden file test for package:flutter.

Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing.

@Piinks – so, this is interesting. I've updated the description of this PR.

The changes made in August seem to have been only half of the changes to make things consistent. This is the other half of the changes that align with the Aug 2024 update.

https://m3.material.io/styles/color/system/overview#785757d4-691b-45dd-b5dc-9d53ec6fbdbf

Specifically these changes: material-foundation/material-color-utilities@03336bf#diff-f0d491177f9e42cf45baea3a37a1694c493d60d17855101af426848634d410eb

FYI: this change does drop the code size of the material sample (minified, uncompressed JS) around ~2k. The changes eliminated several dynamic calls and make things final which allows more more optimization in the compiler

Ok! All that needs doing IMO is creating a one pager on the website to help folks maintain the colors they have when this reaches stable and breaks them. I shared an example above.

@Piinks happy to help, BUT I'm a bit confused how to do it. See the linked diff from the repo. It's not a matter of switching color A for color B. The algorithm used to calculate colors changed.

If I understand correctly, the color roll we did in the fall left us out of sync w/ the algorithm change being brought in here.

@Piinks – FYI/interesting - no goldens are affected here? Hrm...