From c64618a15dadc95a132976c7da75f2ba1edcd8c4 Mon Sep 17 00:00:00 2001 From: Curt Hagenlocher Date: Sun, 15 Nov 2026 16:22:56 -0800 Subject: [PATCH] fix: Verify release candidates under the physical temporary path On macOS the temporary directory is under /var, which is a symlink to /private/var. verify_rc.sh worked under the symlinked path, so tools could see the same files under both paths. On the newer macOS runner image, MSBuild then treated each project as two and built them concurrently into the same outputs, failing with spurious "type or namespace not found" errors. Resolving VERIFY_TMPDIR to its physical path makes every tool see one path. Co-Authored-By: Claude Opus 5.5 --- dev/release/verify_rc.sh | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/dev/release/verify_rc.sh b/dev/release/verify_rc.sh index e2c22941..a470d1b0 100755 --- a/dev/release/verify_rc.sh +++ b/dev/release/verify_rc.sh @@ -73,6 +73,12 @@ setup_tmpdir() { else mkdir -p "${VERIFY_TMPDIR}" fi + + # Work under the physical path. On macOS the temporary directory is under /var, + # which is a symlink to /private/var. Working under the symlinked path lets + # tools see the same files under both paths, and MSBuild then treats each + # project as two and builds them concurrently into the same outputs. + VERIFY_TMPDIR="$(cd "${VERIFY_TMPDIR}" && pwd -P)" } download() {