Fetch tags with --force: the release tag on the server wins
Found in the VM test: when a tag had moved (a re-tagged release), a church's fetch refused it and every later deploy failed its checks. The deploy checks out the tag the Hub asked for, so the remote's tag is the one to trust. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ls1vMdni7EfytGYqQTprME
This commit is contained in:
@@ -217,7 +217,7 @@ install_events() {
|
||||
mkdir -p "$dir"
|
||||
chown "$user:$user" "$dir"
|
||||
run_as "$user" "$dir" git clone --quiet "$CROSSCODE_REPO" .
|
||||
run_as "$user" "$dir" git fetch --tags --quiet origin
|
||||
run_as "$user" "$dir" git fetch --tags --force --quiet origin
|
||||
if [ "$main" = 1 ]; then
|
||||
version=origin/main
|
||||
elif [ -z "$version" ]; then
|
||||
|
||||
Reference in New Issue
Block a user