π OpenHands: AI-Driven Development
fix(docker): ensure `latest` tag always points to latest stable release (#780)
Rohit Malhotra5d7f53930363
diff --git a/.github/workflows/docker.yml b/.github/workflows/docker.ymlindex 6bb8790ec2..386816de5b 100644--- a/.github/workflows/docker.yml+++ b/.github/workflows/docker.yml@@ -314,12 +314,12 @@ jobs:create_manifest "$MANIFEST_TAG"done- # Preserve a latest alias on main pushes.- if [ "${{ github.ref }}" == "refs/heads/main" ]; then- LATEST_TAG="latest"- create_manifest "$LATEST_TAG" "main"- MANIFEST_TAGS+=("$LATEST_TAG")- fi+ # `latest` multi-arch manifest is created automatically above when a+ # stable version tag is pushed (the per-arch build adds `latest-{arch}`+ # tags for non-pre-release tags, and the loop above merges them into a+ # `latest` manifest). We intentionally do NOT alias main to latest here+ # so that `latest` always points at the highest stable tagged release,+ # not at unreleased main-branch code.MANIFEST_TAG_CSV=$(IFS=,; echo "${MANIFEST_TAGS[*]}")echo "manifest_tags=$MANIFEST_TAG_CSV" >> "$GITHUB_OUTPUT"