Skip to content

chore(deps): upgrades left on the table by the 3.0.0 release #167

Closed

Description

@arrrrny

Upgrades the 3.0.0 release did not take, per the dependency-bump rule in AGENTS.md. The publish continued without them; this issue tracks the decision.

Resolved by dart pub outdated on master after the 3.0.0 merge:

Package Current Available Held back by
test (dev, zorphy_migrator) 1.31.2 1.33.0 declared constraint ^1.31.1
clock (transitive) 1.1.2 1.1.3 test_api / clock pins
crypto (transitive) 3.0.7 3.0.8 transitive pin
glob (transitive) 2.1.3 2.2.0 transitive pin
pub_semver (transitive) 2.2.0 2.2.1 transitive pin
stack_trace (transitive) 1.12.1 1.12.2 transitive pin
test_api (transitive) 0.7.13 0.7.15 transitive pin
yaml (transitive) 3.1.3 3.1.4 transitive pin
built_collection (transitive) 5.1.2 6.0.0 major — needs a consumer change

Notes:

  • zorphy and zorphy_annotation themselves report no outdated direct dependencies; zorphy_annotation is fully current.
  • The zorphy_annotation row saying 2.4.6 is a local override (pubspec_overrides.yaml points at ../zorphy_annotation, which is at 3.0.0). It is not a real version lag and must not be "fixed".
  • built_collection 6.0.0 is a major and is not held by our own constraint — it arrives through a dependency. Worth checking whether anything still needs it before widening anything.
  • The test bump is ours to take: raise zorphy_migrator's dev_dependencies.test from ^1.31.1 to ^1.33.0 and re-run dart test -j 2.

Follow-up work, not a blocker: a chore(deps) PR that takes the patch/minor bumps, re-resolves the lockfiles, and re-runs the gates (dart analyze ., both suites, ./scripts/local_ci.sh).

Activity

  1. added
    choremaintenance — refactor, bump, migrate, docs, cleanup
    on Nov 17, 2026
  2. coderabbitai commented on Nov 17, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #163 - chore(deps): record the built_collection 6.0.0 hold decision [merged]


    📝 Issue Planner

    Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.

    • Create Plan

    🧪 Issue enrichment is currently in open beta.

    You can configure auto-planning by selecting labels in the issue_enrichment configuration.

    To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

    issue_enrichment:
      auto_enrich:
        enabled: false

    💬 Have feedback or questions? Drop into our discord!

  3. arrrrny commented on Nov 17, 2026

    @arrrrny
    OwnerAuthor

    ✅ Forklift: shipped — #168

  4. arrrrny commented on Nov 17, 2026

    @arrrrny
    OwnerAuthor

    The built_collection row is now being worked upstream rather than waited on: google/built_value.dart#1406 widens built_value's constraint to >=5.1.1 <7.0.0, matching what code_builder, build_runner and build_daemon already declare. Verified locally against built_collection 6.0.0 — built_value 252 tests, built_value_generator 106, built_value_test 11, analyze clean.

    Sequencing for the zorphy side: once a built_value release carrying that widening is published, the upgrade needs no code change at all — the resolver picks built_collection 6.0.0 by itself. The only edit is deleting the now-stale "held" comment in zorphy/pubspec.yaml:20-25 and re-resolving the lockfile. Until then, adding built_collection: ^6.0.0 to our pubspec.yaml is unsatisfiable (built_value pins ^5.0.0), so it should not be attempted.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    choremaintenance — refactor, bump, migrate, docs, cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions