When deploy.sh itself changes in the commit being pulled, the bash
process is still running the OLD script from memory — git reset --hard
updated the file on disk but the in-memory instructions are stale.
This bit the 2026-04-09 Dalidou deploy: the old pre-build-sha Step 2
ran against fresh source, so the container started with
ATOCORE_BUILD_SHA="unknown" instead of the real commit. Manual
re-run fixed it, but the class of bug will re-emerge every time
deploy.sh itself changes.
Fix (Step 1.5):
- After git reset --hard, sha1 the running script ($0) and the
on-disk copy at $APP_DIR/deploy/dalidou/deploy.sh
- If they differ, export ATOCORE_DEPLOY_REEXECED=1 and exec into
the fresh copy so Step 2 onward runs under the new script
- The sentinel env var prevents recursion
- Skipped in dry-run mode, when $0 isn't readable, or when the
on-disk script doesn't exist yet
Docs (docs/dalidou-deployment.md):
- New "The deploy.sh self-update race" troubleshooting section
explaining the root cause, the Step 1.5 mechanism, what the log
output looks like, and how to opt out
Verified syntax and dry-run. 219/219 tests still passing.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Anto01
03822389a1