From 46e3f5a1277fe355526b24d60e3be95299e6a1d9 Mon Sep 17 00:00:00 2001 From: wtclaude Date: Tue, 18 Aug 2026 07:31:58 -0500 Subject: [PATCH] ci(core-ref): bump the pin past registerTeamProvider MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit `frozen-manifest` has been failing since Teams phase 2, on this PR and on #11 before it, for a reason that has nothing to do with either: the pinned core (website#140, the module-system de-UO slice) predates `api.registerTeamProvider`, which this module has called since phase 1 of its Teams work. The module therefore fails to LOAD in the pinned checkout — "api.registerTeamProvider is not a function" — and a module that does not load adds no routes, which the job correctly reports as the module having removed everything it serves. So the red was real and was pointing at the pin, exactly as the pin's own comment says it should: core moves for reasons that have nothing to do with this module, and a bump is a deliberate commit saying which core the module was last proved against. Bumped to `edge` at Teams phase 3 (website#152) — the first core that has both `registerTeamProvider` and the roster projection this module now implements. Reproduced the whole job locally against that core: core's own manifest is current at the new pin, the module loads, and the difference is 73 routes, all documented. `routes.manifest.json` is unchanged and needed no regeneration, which is the expected result for a client-only change. Not bumped to the phase 4 core, deliberately: that is website#153 and is not merged yet. Nothing in this module needs it — the second slot is a client-side declaration, invisible to the route manifest. Co-Authored-By: Claude --- ci/core-ref.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ci/core-ref.json b/ci/core-ref.json index 9e78853..023530a 100644 --- a/ci/core-ref.json +++ b/ci/core-ref.json @@ -1,6 +1,6 @@ { "$comment": "The core this module is proved against. MODULE_API.md §5.3: the frozen-manifest job clones RunicGateway/website at this exact ref, drops this module in as modules/uo and runs CORE's own routeManifest.js — nothing else can answer whether the URLs the module claims are the URLs it actually serves. Pinned rather than tracking `edge` on purpose: core moves for reasons that have nothing to do with this module, and a bump is then a deliberate commit saying which core the module was last proved against, instead of an unexplained red X on someone else's PR. Bump it, regenerate routes.manifest.json, and commit both together.", "repo": "https://gitea.whitlocktech.com/RunicGateway/website.git", - "ref": "87230c879aa6e9adde3507718aed6bc4e4d86009", - "refName": "edge @ phase 3 slice 4 (website#140)" + "ref": "7ed2ac99838f4bd64e1df324fe4961673648b0e6", + "refName": "edge @ Teams phase 3 (website#152)" }