From abfd6cbffe54d0aea2ac5c73c46cc1abc4cf5983 Mon Sep 17 00:00:00 2001 From: Dov Zimring Date: Tue, 1 Sep 2026 10:45:27 -0700 Subject: [PATCH] Stop re-proposing the two upgrades that have nowhere to land MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Both of these reopen every week, fail the same way, and cost a review each time. Neither is fixable in this repository, so the honest move is to say so in the config rather than let the queue relitigate it. GitHub.Copilot.SDK — ignored outright, not by update-type. SquadAgent.cs uses CopilotClient through Microsoft.Agents.AI.GitHub.Copilot, and MAF 1.11.0-rc1 declares `GitHub.Copilot.SDK [1.0.0, )`. The open range means restore accepts a newer SDK and the compiler then rejects it — CS0012, "defined in an assembly that is not referenced ... Version=1.0.0.0", on net8.0, net9.0 and net10.0 alike. Note the break arrived on 1.0.3 -> 1.0.11, a *patch*, which is why a semver-major ignore would not have caught it. Lift this with MAF: 1.19.0+ declares `[1.0.5, )`. typescript — majors only. typescript-eslint still peer-requires `typescript >=4.8.4 <6.1.0` at 8.69.0, its newest release, so TS 7 has no supported lint toolchain. npm "resolves" the conflict by nesting duplicate @typescript-eslint trees, which means lint:eslint would run a parser against a compiler it does not support — failing quietly rather than loudly, which is worse. Minor and patch TypeScript updates still flow. Both comments name the condition that should retire them, so whoever finds this later can tell whether it still holds. --- .github/dependabot.yml | 27 +++++++++++++++++++++++++++ 1 file changed, 27 insertions(+) diff --git a/.github/dependabot.yml b/.github/dependabot.yml index 6da81d17..27ede6c7 100644 --- a/.github/dependabot.yml +++ b/.github/dependabot.yml @@ -28,6 +28,21 @@ updates: - dependency-name: "OpenTelemetry*" update-types: - "version-update:semver-major" + # GitHub.Copilot.SDK is held at whatever Microsoft.Agents.AI.GitHub.Copilot was + # built against, and is NOT independently upgradable — note this is a full stop, + # not a semver-major one, because the break arrives on a patch bump. + # + # SquadAgent.cs consumes CopilotClient through MAF. MAF 1.11.0-rc1 declares + # `GitHub.Copilot.SDK [1.0.0, )`, so restore happily accepts a newer SDK and the + # compiler then rejects it: `CS0012: The type 'CopilotClient' is defined in an + # assembly that is not referenced ... GitHub.Copilot.SDK, Version=1.0.0.0`. That + # is what 1.0.3 -> 1.0.11 did in #124, on all three target frameworks. + # + # Lift this together with MAF, not before: 1.19.0+ declares `[1.0.5, )` and is + # built against the newer SDK line. The direct PackageReference above is itself a + # workaround pending microsoft/agent-framework#6457, so both are likely to be + # resolved by the same upgrade. + - dependency-name: "GitHub.Copilot.SDK" - package-ecosystem: "nuget" directory: "/test/Squad.Agents.AI.Tests" @@ -82,6 +97,18 @@ updates: update-types: - "minor" - "patch" + ignore: + # TypeScript majors wait on typescript-eslint, which gates the whole lint step. + # Its newest release (8.69.0) still peer-requires `typescript >=4.8.4 <6.1.0`, so + # TS 7 has no supported toolchain to move to: npm resolves the conflict by nesting + # duplicate @typescript-eslint trees, and `npm run lint:eslint` then runs a parser + # against a compiler it does not claim to support. #33 and #26 are that upgrade. + # + # Minor and patch TypeScript updates are unaffected and still flow. Drop this once + # typescript-eslint widens the peer range past 7. + - dependency-name: "typescript" + update-types: + - "version-update:semver-major" # npm — Docs site (Astro/Starlight), which does have its own lockfile. - package-ecosystem: "npm"