RunicGateway/Module-uo
3
0
Fork 0
Code Issues 1 Pull Requests Actions Packages Projects Releases 8 Wiki Activity

ci(core-ref): pin the core on main, now that the cutover has landed #27

Merged
whitlocktech merged 1 commits from ci/core-ref-main into main 2026-09-01 18:03:22 +00:00
Conversation 0 Commits 1 Files Changed 1 +2 -2
1 changed files with 2 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Showing only changes of commit c679944181 - Show all commits

4
ci/core-ref.json
View File

@@ -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": "52eac24d170adbeb7cfb06486bc7512da1173ef9",
"refName": "edge @ MODULE_API 1.9.0, engagement Phase 11b (website#179)"
"ref": "66bb3b9a3fad01112c06f32d931c9bae56d22de6",
"refName": "main @ MODULE_API 1.9.0, the engagement cutover (website#180)"
}