Flutter's package pinning means it can sometimes be impossible to both pass the up-to-date dependencies check and be compatible with Flutter.
For example, my package dart_eval depends on directed_graph, and the latest version of directed_graph (v0.4.0) depends on collection v1.18.0 (its latest stable release).
However, the stable release of flutter_test pins collection to v1.17.2. Therefore, I cannot use the latest version of directed_graph in dart_eval if I want it to be compatible with Flutter projects.
So in exchange for putting in effort to make my package compatible with the stable Flutter SDK, Pana demotes the package by 10 points for not using the latest version of directed_graph. That's pretty nonsensical, imo.
Flutter's package pinning means it can sometimes be impossible to both pass the up-to-date dependencies check and be compatible with Flutter.
For example, my package dart_eval depends on directed_graph, and the latest version of directed_graph (v0.4.0) depends on
collection
v1.18.0 (its latest stable release).However, the stable release of
flutter_test
pinscollection
to v1.17.2. Therefore, I cannot use the latest version of directed_graph in dart_eval if I want it to be compatible with Flutter projects.So in exchange for putting in effort to make my package compatible with the stable Flutter SDK, Pana demotes the package by 10 points for not using the latest version of directed_graph. That's pretty nonsensical, imo.