master: Try to defend against releasing binaries with a hash suffix version

crhodes via Sbcl-commits <[email protected]> Sat, 27 Jun 2026 19:36:54 +0000
Newsgroups gmane.lisp.steel-bank.cvs
Message-ID <[email protected]>
The branch "master" has been updated in SBCL:
       via  cbdaa062e9dc7fde5be207e55a0800a2b7e1a75e (commit)
      from  a248b46823a753e8dbd1fe7a3775d452dd6f7e47 (commit)

- Log -----------------------------------------------------------------
commit cbdaa062e9dc7fde5be207e55a0800a2b7e1a75e
Author: Christophe Rhodes <[email protected]>
Date:   Sat Jun 27 20:34:57 2026 +0100

    Try to defend against releasing binaries with a hash suffix version
    
    (I have only attempted write the check to stop the build if it's
    wrong, not tested it.)
---
 release.sh | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/release.sh b/release.sh
index 97eabffb2..dba2318e3 100755
--- a/release.sh
+++ b/release.sh
@@ -164,6 +164,8 @@ fi
 if [ ! \( -f $SBCL_RELEASE_DIR/sbcl-$VERSION-source.tar -o -f $SBCL_RELEASE_DIR/sbcl-$VERSION-source.tar.bz2 \) ]; then
   cd $SBCL_DIR
   $SBCL_DIR/generate-version.sh
+  ## verify that the generated version is what we expect (has no appended hash)
+  grep -v '^;' version.lisp-expr | grep \"$VERSION\"
   mkdir -p CVS
   sh ./distclean.sh
   rm -rf .git

-----------------------------------------------------------------------


hooks/post-receive
-- 
SBCL