From a9dad3202e4ed4bb4df3cd440294093850124bf8 Mon Sep 17 00:00:00 2001 From: Lakshman Patel Date: Fri, 4 Sep 2026 03:03:43 +0530 Subject: [PATCH] chore: remove deprecated check-submodule-release-parity shim Self-declared deprecated entry point execing check-module-release-parity.sh. Zero references in Makefile, CI, lefthook, docs, or scripts. --- scripts/check-submodule-release-parity.sh | 16 ---------------- 1 file changed, 16 deletions(-) delete mode 100755 scripts/check-submodule-release-parity.sh diff --git a/scripts/check-submodule-release-parity.sh b/scripts/check-submodule-release-parity.sh deleted file mode 100755 index 8efd0c11..00000000 --- a/scripts/check-submodule-release-parity.sh +++ /dev/null @@ -1,16 +0,0 @@ -#!/usr/bin/env bash -set -euo pipefail - -# Deprecated compatibility entry point. The ecosystem is multi-repository; -# use check-module-release-parity.sh for the canonical name. -# -# Workspace release parity: verify every ecosystem module graycode requires -# resolves to a published, reachable commit. This catches go.mod pins to -# versions that do not exist. Run from the graycode repo root. -# -# Note: it deliberately does NOT compare against sibling HEAD ancestry — -# CI clones the siblings as shallow (depth-1) checkouts, so older pinned -# commits are not present in their history and ancestry checks would -# falsely report AHEAD. Resolution (go mod download) is the robust signal. - -exec "$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)/check-module-release-parity.sh" "$@"