Skip to content

Dart CI red on every master commit: analyzer_compat cannot resolve zorphy_annotation ^2.5.0 #164

Closed

Description

@arrrrny

Symptom

Dart CI (.github/workflows/dart.yml, on: push: branches: [master]) has been
red on every master commit since 58f07bc6 (2026-11-15 18:54 UTC):

master commit Dart CI
853040e1 ❌ failure
611e287b ❌ failure
58f07bc6 ❌ failure
ad9f44d4 and earlier ✅ success

Failing jobs: analyzer_compat (13) and analyzer_compat (14), both at the
Install dependencies step:

Because zorphy depends on zorphy_annotation ^2.5.0 which doesn't match any
versions, version solving failed.

Root cause

zorphy/pubspec.yaml declares zorphy_annotation: ^2.5.0, but the newest
published zorphy_annotation on pub.dev is 2.4.6 (no 2.5.0 exists). The
package is developed in-tree at zorphy_annotation/, so any job that resolves it
from pub.dev instead of the local path fails.

The two workflows disagree on exactly that point:

  • .github/workflows/ci.yaml (pull_request) — its analyzer_compat step
    writes zorphy_annotation: path: ../zorphy_annotation into
    zorphy/pubspec_overrides.yaml before dart pub get, so the PR gate is green.
  • .github/workflows/dart.yml (push) — its analyzer_compat step writes only
    the analyzer pin, with no zorphy_annotation path override, so dart pub get reaches for pub.dev and fails.

That is why branch CI can be green while the same tree is red on master.

Suggested fix (one step, mirrors ci.yaml)

In .github/workflows/dart.yml, the Pin analyzer ${{ matrix.analyzer }}.x
step — add the path override to both legs, exactly as ci.yaml does:

if [ "${{ matrix.analyzer }}" = "14" ]; then
  printf 'dependency_overrides:\n  zorphy_annotation:\n    path: ../zorphy_annotation\n  analyzer: ^14.0.0\n  json_serializable:\n    git:\n      url: https://github.com/google/json_serializable.dart\n      path: json_serializable\n' > pubspec_overrides.yaml
else
  printf 'dependency_overrides:\n  zorphy_annotation:\n    path: ../zorphy_annotation\n  analyzer: ^13.0.0\n' > pubspec_overrides.yaml
fi

Not fixed here: this repo's AGENTS.md reserves every PR to the forklift pool
(PR review → Apply review fixes → Merge PR), so the repair is filed for the
pool rather than hand-merged.

Evidence

Discovered while merging #163 (merge task, pool task 7f2e1d49-61bd-4eb3-94cc-3d1cd1e9dd97).

Activity

  1. coderabbitai commented on Nov 16, 2026

    @coderabbitai
    Contributor
    🔗 Related PRs

    #160 - chore(release): zorphy 2.5.0 — SDK floor 3.11 alignment + analyze-clean gate [closed]


    📝 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!

  2. added
    bugSomething isn't working
    choremaintenance — refactor, bump, migrate, docs, cleanup
    on Nov 16, 2026
  3. arrrrny commented on Nov 16, 2026

    @arrrrny
    OwnerAuthor

    ✅ Forklift: shipped — #165

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

    bugSomething isn't workingchoremaintenance — refactor, bump, migrate, docs, cleanup

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions