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
chore(deps): built_collection 6.0.0 available — held by transitive constraint (code_builder) #158
Flagged by dart pub outdated during the 2.4.6 release (2026-11-15).
Held-back upgrade
Package
Current
Latest
Resolvable
built_collection
5.1.2
6.0.0
-
dart pub upgrade --dry-run finds no resolution: 6.0.0 is a major bump and the hold is transitive — code_builder 4.13.0 (already latest) and the build_daemon chain pin built_collection below 6. zorphy declares no direct constraint on it, so this repo's constraint is not what to widen.
Action
Decide whether to wait for code_builder upstream to widen its built_collection constraint, or pursue an upgrade path.
Everything else is current: zorphy_annotation reports no outdated packages; all other direct/dev dependencies are up-to-date.
Decision: wait — but the blocker is built_value, not code_builder
Answering the Action in this issue's body. The premise needs correcting: the
latest code_builder and build_daemonalready allow built_collection
6.0.0, so waiting on code_builder upstream would never release this hold.
Constraints read from the resolved pub cache:
Package
Latest
Constraint on built_collection
code_builder
4.13.0
>=5.1.1 <7.0.0 — allows 6.0.0
build_runner
2.17.1
>=5.1.1 <7.0.0 — allows 6.0.0
build_daemon
4.1.7
>=5.0.0 <7.0.0 — allows 6.0.0
built_value
8.13.0
^5.0.0 — blocks 6.0.0
The sole blocker is built_value, whose every published version (8.10.1 …
8.13.0) pins built_collection: ^5.0.0. built_value 8.13.0 shipped
2026-09-02, before built_collection 6.0.0 (2026-10-26), so this looks like a
release that has not caught up rather than a deliberate hold.
No upgrade path exists in this repo.zorphy declares no direct built_collection constraint, so there is nothing to widen; forcing one fails
resolution outright:
$ dart pub add "built_collection:^6.0.0" --dry-run
Because build_runner >=2.8.0 depends on built_value ^8.10.1 which depends on
built_collection ^5.0.0, build_runner >=2.8.0 requires built_collection ^5.0.0.
So, because zorphy depends on both built_collection ^6.0.0 and build_runner
^2.17.1, version solving failed.
Upstream request filed: google/built_value.dart#1405 (widen to >=5.1.1 <7.0.0,
matching code_builder/build_runner). Note 6.0.0 is a real breaking major — BuiltList.asList / BuiltMap.asMap return unmodifiable views instead of
copies — so the widening may need code changes there.
The decision is recorded in-tree in #163 so the next release pass does not
re-investigate code_builder.
Closed by merged PR #163 (13a95c4), which records the hold decision for built_collection 6.0.0 in zorphy/pubspec.yaml. The unblock is tracked upstream at google/built_value.dart#1405.
Activity
arrrrny commentedon Nov 16, 2026
✅ Forklift: shipped — #163
arrrrny commentedon Nov 16, 2026
Decision: wait — but the blocker is
built_value, notcode_builderAnswering the Action in this issue's body. The premise needs correcting: the
latest
code_builderandbuild_daemonalready allowbuilt_collection6.0.0, so waiting on
code_builderupstream would never release this hold.Constraints read from the resolved pub cache:
built_collectioncode_builder>=5.1.1 <7.0.0— allows 6.0.0build_runner>=5.1.1 <7.0.0— allows 6.0.0build_daemon>=5.0.0 <7.0.0— allows 6.0.0built_value^5.0.0— blocks 6.0.0The sole blocker is
built_value, whose every published version (8.10.1 …8.13.0) pins
built_collection: ^5.0.0.built_value8.13.0 shipped2026-09-02, before
built_collection6.0.0 (2026-10-26), so this looks like arelease that has not caught up rather than a deliberate hold.
No upgrade path exists in this repo.
zorphydeclares no directbuilt_collectionconstraint, so there is nothing to widen; forcing one failsresolution outright:
Upstream request filed: google/built_value.dart#1405 (widen to
>=5.1.1 <7.0.0,matching
code_builder/build_runner). Note 6.0.0 is a real breaking major —BuiltList.asList/BuiltMap.asMapreturn unmodifiable views instead ofcopies — so the widening may need code changes there.
The decision is recorded in-tree in #163 so the next release pass does not
re-investigate
code_builder.arrrrny commentedon Nov 16, 2026
Closed by merged PR #163 (13a95c4), which records the hold decision for built_collection 6.0.0 in zorphy/pubspec.yaml. The unblock is tracked upstream at google/built_value.dart#1405.