Repository navigation
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔵📐 Cosmetic only — no change requested. The sentence "
built_collection5.1.2 -> 6.0.0 is held, and NOT by this constraint" sits directly abovecode_builder: ^4.10.0(line 27), so a reader who lands on the pin first can read "this constraint" as that one. The full sentence makes the intended meaning clear (no directbuilt_collectionconstraint exists anywhere in this file), so I would not block on it. Verified independently:built_value8.13.0 is indeed the sole blocker,code_builder4.13.0 /build_runner2.17.1 /build_daemon4.1.7 all allow 6.0.0, and the quoted solver error reproduces verbatim. The 6.0.0 breaking-change note also matches the published changelog.