Why: the parent must pin the merged component SHAs so the combined build and CI gate run against the delivered U2 code and U1 runbook. Evidence: backend origin-main merge commit of #137 and documents origin-main merge commit of #61 (fetched post-merge, replacing a stale pre-merge pin attempt). Impact: gitlink updates only. Refs: backend PR #137; documents PR #61.
This commit is contained in:
+1
-1
Submodule modules/backend updated: ea4651b1f8...2497508271
+1
-1
Submodule modules/documents updated: 95e5c9d307...3e2d8c9049
Reference in New Issue
Block a user