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
@@ -32,7 +32,7 @@ git -C "$out" init --quiet
 git -C "$out" remote add origin "$repository"
 git -C "$out" fetch --quiet --no-tags --depth=1 origin "+${ref}:refs/remotes/pinned" ||
  fail "cannot fetch the pinned platform ref."
-[[ "$(git -C "$out" rev-parse refs/remotes/pinned)" == "$commit" ]] ||
+[[ "$(git -C "$out" rev-parse "refs/remotes/pinned^{commit}")" == "$commit" ]] ||
  fail "the pinned ref does not resolve to EKKLESIA_PLATFORM_COMMIT."
 git -C "$out" -c advice.detachedHead=false checkout --quiet --detach "$commit"
 rm -rf "$out/.git"