You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
flutter-analyze-try has been failing for ~24h #179296
A green result from the flutter-analyze-try bot is a prerequisite for landing changes to the dart analyzer (and related packages), so this problem is blocking a nontrivial subset of dart development work.
Sorry, I didn't have any context on why they were added, and assumed (since removing them after updating didn't trip any warnings) that the APIs were experimental in older versions, and had graduated out.
I'm confused though after reading the things linked above, because the quoted text in the description of #177393 sounds like that is indeed what happened. With the upper bound relaxed, why is this still an issue upstream? And/or: why is this happening upstream but not in flutter/packages if this analyzer feature has already landed?
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 -v and a minimal reproduction of the issue.
Activity
stereotype441 commentedon Dec 1, 2025
FYI @Piinks @stuartmorgan-g @chunhtai
stuartmorgan-g commentedon Dec 1, 2025
Sorry, I didn't have any context on why they were added, and assumed (since removing them after updating didn't trip any warnings) that the APIs were experimental in older versions, and had graduated out.
I'm confused though after reading the things linked above, because the quoted text in the description of #177393 sounds like that is indeed what happened. With the upper bound relaxed, why is this still an issue upstream? And/or: why is this happening upstream but not in flutter/packages if this analyzer feature has already landed?
stuartmorgan-g commentedon Dec 1, 2025
Oh, I see now that it's running
downgrade. And we only rundowngradeon stable, whereas this is adowngraderun on master.[go_router_builder] Require analyzer 8.2 (flutter#10546)
github-actions commentedon Dec 15, 2025
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.[go_router_builder] Require analyzer 8.2 (flutter#10546)
[go_router_builder] Require analyzer 8.2 (flutter#10546)