RAGFlow is an agent-native database: a Retrieval-Augmented Generation (RAG) engine that grew into context infrastructure.
Go agent-harnessagent-native-databaseagentic-aiagentic-retrievalagentic-searchaiai-agentscontext-enginecontext-engineeringcontext-managementharness-engineeringknowledge-compilationragretrieval-augmented-generationretrieval-harnesssearch-harness
release dockerhub image remove unnecessary tag (#21860)
maoyifeng7ee683a2c266
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 83d323392f..248c090111 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -267,9 +267,10 @@ jobs:# Build the linux/amd64 image on a GitHub-hosted runner, mirroring# `build-arm64`. Pushes the version tag (amd64-only) so amd64 pulls always- # work even if the ARM64 job fails, plus the arch-specific -amd64/:amd64 tags- # for direct pulls. The multi-arch manifest is created by the `build-arm64`- # job once both arches are pushed.+ # work even if the ARM64 job fails. The arch-specific -amd64/:amd64 tags are+ # intermediate only: the `build-arm64` job creates the public multi-arch+ # manifest list and then deletes them from Docker Hub, leaving only the+ # version/latest/nightly dual-structure tags.build-amd64:needs:- prepare@@ -310,14 +311,16 @@ jobs:GOPROXY=https://proxy.golang.org,directtags: |infiniflow/ragflow:${{ needs.prepare.outputs.release_tag }}-amd64- infiniflow/ragflow:amd64infiniflow/ragflow:${{ needs.prepare.outputs.release_tag }}# Build the linux/arm64 image on a GitHub-hosted ARM64 runner and merge it# with the amd64 image (pushed by the `build-amd64` job above) into a single# multi-arch manifest list for infiniflow/ragflow:${RELEASE_TAG} and :latest,# so `docker pull infiniflow/ragflow:${RELEASE_TAG}` resolves per-arch on both- # platforms. Runs after `build-amd64` so the amd64 (-amd64/:amd64) tags exist.+ # platforms. Runs after `build-amd64` so the amd64 -amd64 tag exists.+ # After the manifest is published, the intermediate -amd64/-arm64 tags are+ # deleted from Docker Hub, leaving only the dual-structure tags+ # (${RELEASE_TAG}, :latest for stable, or :nightly).build-arm64:needs:- build-amd64@@ -365,15 +368,17 @@ jobs:GOPROXY=https://proxy.golang.org,directtags: |infiniflow/ragflow:${{ needs.prepare.outputs.release_tag }}-arm64- infiniflow/ragflow:arm64# Create/upgrade the public multi-arch tags now that both arch-specific- # images (-amd64/:amd64 from the `build-amd64` job, -arm64/:arm64 from this- # job) are pushed. :${RELEASE_TAG} was already pushed amd64-only by the- # build-amd64 job (so amd64 pulls always work); this upgrades it to multi-arch.+ # images (-amd64 from the `build-amd64` job, -arm64 from this job) are+ # pushed. :${RELEASE_TAG} was already pushed amd64-only by the build-amd64+ # job (so amd64 pulls always work); this upgrades it to multi-arch.# :latest is created here for the first time this release (it is NOT pushed# by the build-amd64 job), so the previous, possibly multi-arch, :latest is- # never overwritten with an amd64-only image before ARM64 is ready.+ # never overwritten with an amd64-only image before ARM64 is ready. Both+ # :${RELEASE_TAG} and :latest are assembled from this run's release-specific+ # -amd64/-arm64 tags, so overlapping runs for other refs cannot race on the+ # shared mutable amd64/arm64 tags.- name: Create multi-arch manifestrun: |docker buildx imagetools create --tag infiniflow/ragflow:${RELEASE_TAG} \@@ -384,9 +389,59 @@ jobs:# not overwrite the stable :latest.if [ "${PRERELEASE}" != "true" ]; thendocker buildx imagetools create --tag infiniflow/ragflow:latest \- infiniflow/ragflow:amd64 \- infiniflow/ragflow:arm64+ infiniflow/ragflow:${RELEASE_TAG}-amd64 \+ infiniflow/ragflow:${RELEASE_TAG}-arm64elseecho "RELEASE_TAG=${RELEASE_TAG} is a prerelease/nightly build; skipping :latest update."fi+ # The -amd64/-arm64 single-arch tags are intermediate steps used to assemble+ # the multi-arch manifest above. They are release-specific, so no other+ # workflow run references them. Delete them from Docker Hub so the published+ # repository exposes only the dual-structure tags (${RELEASE_TAG}, :latest+ # for stable, or :nightly). The Docker Hub tag-delete API removes the tag+ # name while keeping the manifest referenced by the multi-arch index, so the+ # public tags stay intact for per-arch pulls.+ - name: Remove intermediate per-arch tags+ env:+ DH_USER: infiniflow+ DH_TOKEN: ${{ secrets.DOCKERHUB_TOKEN }}+ run: |+ set -euo pipefail+ JWT=$(curl -fsS -X POST -H "Content-Type: application/json" \+ -d "{\"username\":\"${DH_USER}\",\"password\":\"${DH_TOKEN}\"}" \+ https://hub.docker.com/v2/users/login/ | jq -r .token) || true+ if [ -z "${JWT}" ] || [ "${JWT}" = "null" ]; then+ echo "::error::Failed to obtain Docker Hub JWT; check DOCKERHUB_TOKEN can authenticate to the Hub API"+ exit 1+ fi+ FAILED_TAGS=""+ delete_tag() {+ local tag="$1"+ # Capture the HTTP status instead of failing on 404 (-f would make+ # curl exit non-zero on 404 and abort the step under set -e). A tag+ # that was never pushed is fine; only real failures should surface.+ local code+ code=$(curl -sS -o /dev/null -w "%{http_code}" -X DELETE \+ -H "Authorization: JWT ${JWT}" \+ "https://hub.docker.com/v2/repositories/${DH_USER}/ragflow/tags/${tag}/" \+ || echo "000")+ case "${code}" in+ 200|202|204)+ echo "Deleted Docker Hub tag: ${tag}"+ ;;+ 404)+ echo "Docker Hub tag already absent: ${tag}"+ ;;+ *)+ echo "::warning::Failed to delete Docker Hub tag ${tag} (HTTP ${code})"+ FAILED_TAGS="${FAILED_TAGS} ${tag}"+ ;;+ esac+ }+ delete_tag "${RELEASE_TAG}-amd64"+ delete_tag "${RELEASE_TAG}-arm64"+ if [ -n "${FAILED_TAGS}" ]; then+ echo "::warning::Some intermediate tags could not be removed and may linger on Docker Hub:${FAILED_TAGS}"+ fi+