ci: pin the platform harness to the released Core v0.2.5

Integration still fetched Core at PR #92's head (5e9433d): the right pin while that PR was in review, but it predates #94 (display credential renewal) and #93 (the registry move), both in v0.2.5. Signage now proves itself against the release it will run on. The pin contract also accepts a release tag (refs/tags/vX.Y.Z) alongside a pull request head or main, and the fetch compares the ref's commit (^{commit}) so an annotated tag pins the same way a lightweight one does. v0.2.5 is lightweight; that should not be a hidden requirement. Co-Authored-By: Claude Opus 5.5 <[email protected]>
2026-10-14 00:05:15 -05:00
parent ba4821ec63
commit c1213dad08
4 changed files with 9 additions and 8 deletions
@@ -1,5 +1,6 @@
-# The companion Core harness Signage uses to install and run its real external package. The pull ref
-# remains reachable after its branch is deleted; the full commit pin makes the checkout immutable.
+# The companion Core harness Signage uses to install and run its real external package: a released
+# Core, by its tag. A pull request's ref (refs/pull/N/head) is used only while Signage depends on a
+# Core change still in review. The full commit pin makes the checkout immutable either way.
 EKKLESIA_PLATFORM_REPOSITORY=https://git.zayin.net/Zayin/Ekklesia.git
-EKKLESIA_PLATFORM_REF=refs/pull/92/head
-EKKLESIA_PLATFORM_COMMIT=5e9433d96b413117374a6132d89400867414c2c8
+EKKLESIA_PLATFORM_REF=refs/tags/v0.2.5
+EKKLESIA_PLATFORM_COMMIT=437720f2286e962829f2ec8c1c6137ea24f87b9f