Bump dart_pub to 0.0.9 to restore pub points - #17
Open
Rexios80 wants to merge 1 commit into
Open
Conversation
Restore the 10 pub points lost when the pinned 0.0.8 constraint fell behind dart_pub 0.0.9. The solver/cache APIs puby uses are unchanged. Bump rexios_lints to ^18.1.0 so analyzer 14 can resolve. Co-authored-by: Rexios <rexios@rexios.dev>
Rexios80
marked this pull request as ready for review
August 31, 2026 13:11
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
puby 1.39.0 first dropped 160 → 150 after the pana “up-to-date dependencies” grace expired on the exact pin
dart_pub: 0.0.8(latest0.0.9).A later pub.dev re-analysis (2026-08-31T20:05:55Z) took the published 1.39.0 from 150 → 70/160. The extra −80 is one timeout cascade, not four separate package bugs:
dart pub get/dart pub outdatedexceeded pana’s 2:00 sandbox timeoutpub downgradestill passed on that same run, so the graph itself is solvableChecked locally on this branch and on published 1.39.0:
dart pub getanddart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overridesboth finish in ~0.3–1.3s. No resolver loop or hang. 1.39.0’s only real constraint issue is stilldart_pub0.0.8 vs 0.0.9.dart_pub0.0.9 is a drop-in for the solver/cache APIs puby uses. The pin stays exact (0.0.9) because dart_pub asks dependents to pin.rexios_lintsis bumped to^18.1.0so analyzer 14 resolves (dev_dependency only; not scored).No extra code changes for the −80. Publishing 1.39.1 should restore 160/160: this branch already scores 160/160 with local pana 0.23.18 (same as pub.dev), including get/outdated well inside the 2-minute budget.
Test plan
dart pub getresolves withdart_pub0.0.9 andrexios_lints^18.1.0 (~0.3s)dart pub get/outdatedalso succeed locally (~1.3s); no hangdart analyze --fatal-infosis cleandart format --set-exit-if-changed .is cleandart pub outdated --no-dev-dependencies --up-to-date --no-dependency-overridesshowsdart_pub0.0.9 / latest 0.0.9pana --no-warning --exit-code-threshold 0→ 160/160 (re-run 2026-09-01, 63s)config_test,projects_test,unknown_command_test,exec_test)dart test, pana)