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: move release workflow from self-hosts to github runner hosts (#21155)
maoyifengcf406b8b6fca
diff --git a/.github/workflows/release.yml b/.github/workflows/release.ymlindex 807119de6c..9a179ae178 100644--- a/.github/workflows/release.yml+++ b/.github/workflows/release.yml@@ -24,30 +24,24 @@ concurrency:jobs:prepare:- runs-on: [ "self-hosted", "ragflow-release" ]+ runs-on: ubuntu-24.04outputs:release_tag: ${{ steps.release.outputs.release_tag }}prerelease: ${{ steps.release.outputs.prerelease }}steps:- - name: Ensure workspace ownership- run: echo "chown -R ${USER} ${GITHUB_WORKSPACE}" && sudo chown -R ${USER} ${GITHUB_WORKSPACE}-# https://github.com/actions/checkout/blob/v6/README.md+ # Keep `token` so the move-mutable-tag step (schedule/nightly) can+ # `git push -f` via the persisted GITHUB_TOKEN (persist-credentials+ # defaults to true). Workflow-level `permissions: contents: write`+ # grants the push.- name: Check out codeuses: actions/checkout@v6with:- token: ${{ secrets.GITHUB_TOKEN }} # Use the secret as an environment variable+ token: ${{ secrets.GITHUB_TOKEN }}fetch-depth: 0fetch-tags: true- # https://github.com/actions/setup-go- - name: Set up Go- uses: actions/setup-go@v5- with:- go-version-file: go.mod- cache: true-- name: Prepare release metadataid: releaserun: |@@ -203,17 +197,13 @@ jobs:needs:- prepare- build_cli- runs-on: [ "self-hosted", "ragflow-release" ]+ runs-on: ubuntu-24.04steps:- - name: Ensure workspace ownership- run: echo "chown -R ${USER} ${GITHUB_WORKSPACE}" && sudo chown -R ${USER} ${GITHUB_WORKSPACE}-# https://github.com/actions/checkout/blob/v6/README.md- name: Check out codeuses: actions/checkout@v6with:- token: ${{ secrets.GITHUB_TOKEN }}fetch-depth: 0fetch-tags: true@@ -252,60 +242,85 @@ jobs:tools/scripts/install.shtools/scripts/install.ps1+ # Publish the ragflow Python SDK to PyPI. Runs on a GitHub-hosted runner so+ # it no longer depends on the self-hosted release runner. Only stable v* tags+ # (not nightly/prerelease) publish, per the `if` below.release:needs:- prepare- - publish_cli_assets- runs-on: [ "self-hosted", "ragflow-release" ]- env:- RELEASE_TAG: ${{ needs.prepare.outputs.release_tag }}-+ runs-on: ubuntu-24.04steps:- - name: Ensure workspace ownership- run: echo "chown -R ${USER} ${GITHUB_WORKSPACE}" && sudo chown -R ${USER} ${GITHUB_WORKSPACE}-# https://github.com/actions/checkout/blob/v6/README.md- name: Check out codeuses: actions/checkout@v6with:- token: ${{ secrets.GITHUB_TOKEN }}fetch-depth: 0fetch-tags: true-- # Hybrid publishing strategy:- # - Push the version-specific tag :${RELEASE_TAG} (amd64-only) here, so the- # new release is always pullable on amd64 even if the ARM64 job fails.- # Each release uses a unique version tag, so this never clobbers a- # different version's image.- # - Do NOT push :latest here; the existing (possibly multi-arch) :latest- # must not be overwritten with an amd64-only image before ARM64 is ready.- # :latest is created as a multi-arch tag by the `build-arm64` job's- # manifest step once both arches are pushed.- # - Arch-specific tags (-amd64/:amd64) are also pushed for direct pulls.- - name: Build and push image- run: |- sudo docker login --username infiniflow --password-stdin <<< ${{ secrets.DOCKERHUB_TOKEN }}- sudo docker build -t infiniflow/ragflow:${RELEASE_TAG}-amd64 -f Dockerfile .- sudo docker tag infiniflow/ragflow:${RELEASE_TAG}-amd64 infiniflow/ragflow:${RELEASE_TAG}- sudo docker tag infiniflow/ragflow:${RELEASE_TAG}-amd64 infiniflow/ragflow:amd64- sudo docker push infiniflow/ragflow:${RELEASE_TAG}-amd64- sudo docker push infiniflow/ragflow:${RELEASE_TAG}- sudo docker push infiniflow/ragflow:amd64+ - name: Install uv+ uses: astral-sh/setup-uv@v5- name: Build and push ragflow-sdkif: startsWith(github.ref, 'refs/tags/v')run: |cd sdk/python && uv build && uv publish --token ${{ secrets.PYPI_API_TOKEN }}+ # 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.+ build-amd64:+ needs:+ - prepare+ runs-on: ubuntu-24.04+ env:+ RELEASE_TAG: ${{ needs.prepare.outputs.release_tag }}+ steps:+ - name: Check out code+ uses: actions/checkout@v6+ with:+ fetch-depth: 0+ fetch-tags: true++ - name: Set up Docker Buildx+ uses: docker/setup-buildx-action@v3++ - name: Login to Docker Hub+ uses: docker/login-action@v3+ with:+ username: infiniflow+ password: ${{ secrets.DOCKERHUB_TOKEN }}++ - name: Build and push amd64 image+ uses: docker/build-push-action@v6+ with:+ context: .+ file: ./Dockerfile+ platforms: linux/amd64+ push: true+ # Disable build attestations (provenance/SBOM) for the same reason as+ # build-arm64: keep a clean manifest so the multi-arch index merged+ # below contains only amd64 + arm64 image manifests.+ provenance: false+ sbom: false+ # Use a Go proxy that is reliable from GitHub-hosted runners; the+ # Dockerfile default (goproxy.cn) is flaky here (HTTP/2 GOAWAY).+ build-args: |+ GOPROXY=https://proxy.golang.org,direct+ tags: |+ infiniflow/ragflow:${{ needs.prepare.outputs.release_tag }}-amd64+ infiniflow/ragflow:amd64+ infiniflow/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 `release` job above) into a single+ # 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 `release` so the amd64 (-amd64/:amd64) tags exist.+ # platforms. Runs after `build-amd64` so the amd64 (-amd64/:amd64) tags exist.build-arm64:needs:- - release+ - build-amd64- prepareruns-on: ubuntu-24.04-armenv:@@ -353,11 +368,11 @@ jobs:infiniflow/ragflow:arm64# Create/upgrade the public multi-arch tags now that both arch-specific- # images (-amd64/:amd64 from the `release` job, -arm64/:arm64 from this+ # images (-amd64/:amd64 from the `build-amd64` job, -arm64/:arm64 from this# job) are pushed. :${RELEASE_TAG} was already pushed amd64-only by the- # release job (so amd64 pulls always work); this upgrades it to multi-arch.+ # 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 release job), so the previous, possibly multi-arch, :latest is+ # by the build-amd64 job), so the previous, possibly multi-arch, :latest is# never overwritten with an amd64-only image before ARM64 is ready.- name: Create multi-arch manifestrun: |