Docs: Update version references to v0.25.0 in READMEs and docs#14257
Conversation
- Update version tags in README files (including translations) from v0.24.0 to v0.25.0 - Modify Docker image references and documentation to reflect new version - Update version badges and image descriptions - Maintain consistency across all language variants of README files
📝 WalkthroughWalkthroughThis pull request updates version references throughout the codebase from v0.24.0 to v0.25.0, including Docker image tags, package versions, documentation examples, and configuration files across all languages and deployment platforms. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~4 minutes Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 5
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
docker/.env (1)
20-20:⚠️ Potential issue | 🟠 MajorSet
DOC_ENGINEdefault toinfinityto satisfy repository policy.Line 20 still defaults to Elasticsearch, which conflicts with the required project rule for
docker/.env.Proposed fix
-DOC_ENGINE=${DOC_ENGINE:-elasticsearch} +DOC_ENGINE=${DOC_ENGINE:-infinity}As per coding guidelines, "Set
DOC_ENGINE=infinityindocker/.envto switch from Elasticsearch to Infinity engine".🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@docker/.env` at line 20, The DOC_ENGINE default in docker/.env is still set to "elasticsearch"; update the default environment variable DOC_ENGINE=${DOC_ENGINE:-elasticsearch} to use "infinity" instead by changing the default value to DOC_ENGINE=${DOC_ENGINE:-infinity} so the system uses the Infinity engine when DOC_ENGINE is not set.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@docker/README.md`:
- Around line 81-82: The docs currently show the environment variable as
"RAGFLOW-IMAGE" which mismatches the rest of the project; replace the hyphenated
token "RAGFLOW-IMAGE" with the underscore form "RAGFLOW_IMAGE" in the README
text and ensure the default value text still reads "Defaults to
`infiniflow/ragflow:v0.25.0`", updating any other occurrences to match the .env
and docs usage so the env var name is consistent across the project.
In `@docs/administrator/configurations.md`:
- Line 106: The documentation line that reads "The Docker image edition.
Defaults to `infiniflow/ragflow:v0.25.0`" is inconsistent with the actual
default in docker/.env (`infiniflow/ragflow:latest`); update the doc string to
match the runtime default by changing the default value text to
`infiniflow/ragflow:latest` (or alternatively update docker/.env to use
`infiniflow/ragflow:v0.25.0` if you intend to lock the runtime), ensuring the
phrasing around the default remains accurate.
In `@README_pt_br.md`:
- Line 195: The sentence contains a missing space before the inline code token
"edição`v0.25.0`"; update the README_pt_br.md text to add a space so it reads
"edição `v0.25.0`" (preserving the rest of the sentence that references
RAGFLOW_IMAGE and docker/.env) to fix the spacing/typography issue.
In `@README_tzh.md`:
- Around line 194-196: The CAUTION blockquote in README_tzh.md contains a blank
line that triggers markdownlint MD028; fix it by removing the empty line so the
fenced code block directly follows the blockquote text (e.g., ensure the line
after "執行以下指令會自動下載 RAGFlow Docker 映像 `v0.25.0`..." contains "```bash"
immediately with no blank line), keep the language tag (bash) on the opening
fence and close the fence properly, and ensure there are no extra blank lines
inside that blockquote section so the blockquote lines are contiguous.
In `@tools/scripts/README.md`:
- Line 290: Update the example version-to-directory mapping so the semantic
version matches the directory suffix: change the mapping text that currently
shows "Version `v0.25.0` → Directory `tools/migrate/v0_24_0/`" to use
`tools/migrate/v0_25_0/` so the displayed directory reflects the same patch
number as the version string.
---
Outside diff comments:
In `@docker/.env`:
- Line 20: The DOC_ENGINE default in docker/.env is still set to
"elasticsearch"; update the default environment variable
DOC_ENGINE=${DOC_ENGINE:-elasticsearch} to use "infinity" instead by changing
the default value to DOC_ENGINE=${DOC_ENGINE:-infinity} so the system uses the
Infinity engine when DOC_ENGINE is not set.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: 6f463452-b757-49c1-9bdc-f35ff80fea82
⛔ Files ignored due to path filters (3)
admin/client/uv.lockis excluded by!**/*.locksdk/python/uv.lockis excluded by!**/*.lockuv.lockis excluded by!**/*.lock
📒 Files selected for processing (27)
README.mdREADME_ar.mdREADME_fr.mdREADME_id.mdREADME_ja.mdREADME_ko.mdREADME_pt_br.mdREADME_tr.mdREADME_tzh.mdREADME_zh.mdadmin/client/README.mdadmin/client/pyproject.tomldocker/.envdocker/README.mddocs/administrator/admin/ragflow_cli.mddocs/administrator/configurations.mddocs/administrator/upgrade_ragflow.mdxdocs/develop/build_docker_image.mdxdocs/guides/dataset/configure_knowledge_base.mddocs/guides/manage_files.mddocs/quickstart.mdxhelm/values.yamlpyproject.tomlsdk/python/pyproject.tomltest/README.mdtools/scripts/README.mdtools/scripts/db_schema_sync.py
| - `RAGFLOW-IMAGE` | ||
| The Docker image edition. Defaults to `infiniflow/ragflow:v0.24.0`. The RAGFlow Docker image does not include embedding models. | ||
| The Docker image edition. Defaults to `infiniflow/ragflow:v0.25.0`. The RAGFlow Docker image does not include embedding models. |
There was a problem hiding this comment.
Use RAGFLOW_IMAGE (underscore) for env var naming.
The key shown on Line 81 is RAGFLOW-IMAGE, but docs and .env usage elsewhere use RAGFLOW_IMAGE. This can cause misconfiguration when users copy the variable name.
✏️ Suggested doc fix
-- `RAGFLOW-IMAGE`
+- `RAGFLOW_IMAGE`
The Docker image edition. Defaults to `infiniflow/ragflow:v0.25.0`. The RAGFlow Docker image does not include embedding models.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| - `RAGFLOW-IMAGE` | |
| The Docker image edition. Defaults to `infiniflow/ragflow:v0.24.0`. The RAGFlow Docker image does not include embedding models. | |
| The Docker image edition. Defaults to `infiniflow/ragflow:v0.25.0`. The RAGFlow Docker image does not include embedding models. | |
| - `RAGFLOW_IMAGE` | |
| The Docker image edition. Defaults to `infiniflow/ragflow:v0.25.0`. The RAGFlow Docker image does not include embedding models. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docker/README.md` around lines 81 - 82, The docs currently show the
environment variable as "RAGFLOW-IMAGE" which mismatches the rest of the
project; replace the hyphenated token "RAGFLOW-IMAGE" with the underscore form
"RAGFLOW_IMAGE" in the README text and ensure the default value text still reads
"Defaults to `infiniflow/ragflow:v0.25.0`", updating any other occurrences to
match the .env and docs usage so the env var name is consistent across the
project.
| The port used to expose RAGFlow's HTTP API service to the host machine, allowing **external** access to the service running inside the Docker container. Defaults to `9380`. | ||
| - `RAGFLOW-IMAGE` | ||
| The Docker image edition. Defaults to `infiniflow/ragflow:v0.24.0` (the RAGFlow Docker image without embedding models). | ||
| The Docker image edition. Defaults to `infiniflow/ragflow:v0.25.0` (the RAGFlow Docker image without embedding models). |
There was a problem hiding this comment.
Default value is inconsistent with docker/.env and may mislead operators.
Line 106 says the default is infiniflow/ragflow:v0.25.0, but docker/.env currently defaults to infiniflow/ragflow:latest. Please align docs with actual behavior (or update .env default accordingly).
Proposed doc-only fix
- The Docker image edition. Defaults to `infiniflow/ragflow:v0.25.0` (the RAGFlow Docker image without embedding models).
+ The Docker image edition. Defaults to `infiniflow/ragflow:latest` (the RAGFlow Docker image without embedding models).📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| The Docker image edition. Defaults to `infiniflow/ragflow:v0.25.0` (the RAGFlow Docker image without embedding models). | |
| The Docker image edition. Defaults to `infiniflow/ragflow:latest` (the RAGFlow Docker image without embedding models). |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@docs/administrator/configurations.md` at line 106, The documentation line
that reads "The Docker image edition. Defaults to `infiniflow/ragflow:v0.25.0`"
is inconsistent with the actual default in docker/.env
(`infiniflow/ragflow:latest`); update the doc string to match the runtime
default by changing the default value text to `infiniflow/ragflow:latest` (or
alternatively update docker/.env to use `infiniflow/ragflow:v0.25.0` if you
intend to lock the runtime), ensuring the phrasing around the default remains
accurate.
| > Se você estiver usando uma plataforma ARM64, por favor, utilize [este guia](https://ragflow.io/docs/dev/build_docker_image) para construir uma imagem Docker compatível com o seu sistema. | ||
|
|
||
| > O comando abaixo baixa a edição`v0.24.0` da imagem Docker do RAGFlow. Consulte a tabela a seguir para descrições de diferentes edições do RAGFlow. Para baixar uma edição do RAGFlow diferente da `v0.24.0`, atualize a variável `RAGFLOW_IMAGE` conforme necessário no **docker/.env** antes de usar `docker compose` para iniciar o servidor. | ||
| > O comando abaixo baixa a edição`v0.25.0` da imagem Docker do RAGFlow. Consulte a tabela a seguir para descrições de diferentes edições do RAGFlow. Para baixar uma edição do RAGFlow diferente da `v0.25.0`, atualize a variável `RAGFLOW_IMAGE` conforme necessário no **docker/.env** antes de usar `docker compose` para iniciar o servidor. |
There was a problem hiding this comment.
Fix spacing typo in Portuguese sentence.
Line 195 is missing a space before the inline code token (ediçãov0.25.0``), which hurts readability.
Proposed fix
- > O comando abaixo baixa a edição`v0.25.0` da imagem Docker do RAGFlow.
+ > O comando abaixo baixa a edição `v0.25.0` da imagem Docker do RAGFlow.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| > O comando abaixo baixa a edição`v0.25.0` da imagem Docker do RAGFlow. Consulte a tabela a seguir para descrições de diferentes edições do RAGFlow. Para baixar uma edição do RAGFlow diferente da `v0.25.0`, atualize a variável `RAGFLOW_IMAGE` conforme necessário no **docker/.env** antes de usar `docker compose` para iniciar o servidor. | |
| > O comando abaixo baixa a edição `v0.25.0` da imagem Docker do RAGFlow. Consulte a tabela a seguir para descrições de diferentes edições do RAGFlow. Para baixar uma edição do RAGFlow diferente da `v0.25.0`, atualize a variável `RAGFLOW_IMAGE` conforme necessário no **docker/.env** antes de usar `docker compose` para iniciar o servidor. |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README_pt_br.md` at line 195, The sentence contains a missing space before
the inline code token "edição`v0.25.0`"; update the README_pt_br.md text to add
a space so it reads "edição `v0.25.0`" (preserving the rest of the sentence that
references RAGFLOW_IMAGE and docker/.env) to fix the spacing/typography issue.
| > 執行以下指令會自動下載 RAGFlow Docker 映像 `v0.25.0`。請參考下表查看不同 Docker 發行版的說明。如需下載不同於 `v0.25.0` 的 Docker 映像,請在執行 `docker compose` 啟動服務之前先更新 **docker/.env** 檔案內的 `RAGFLOW_IMAGE` 變數。 | ||
|
|
||
| ```bash |
There was a problem hiding this comment.
Fix markdownlint MD028 in the CAUTION blockquote section.
The blockquote near Line 194 includes a blank-line pattern that triggers no-blanks-blockquote.
Proposed fix
> 執行以下指令會自動下載 RAGFlow Docker 映像 `v0.25.0`。請參考下表查看不同 Docker 發行版的說明。如需下載不同於 `v0.25.0` 的 Docker 映像,請在執行 `docker compose` 啟動服務之前先更新 **docker/.env** 檔案內的 `RAGFLOW_IMAGE` 變數。
-
```bash
$ cd ragflow/docker📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| > 執行以下指令會自動下載 RAGFlow Docker 映像 `v0.25.0`。請參考下表查看不同 Docker 發行版的說明。如需下載不同於 `v0.25.0` 的 Docker 映像,請在執行 `docker compose` 啟動服務之前先更新 **docker/.env** 檔案內的 `RAGFLOW_IMAGE` 變數。 | |
| ```bash | |
| > 執行以下指令會自動下載 RAGFlow Docker 映像 `v0.25.0`。請參考下表查看不同 Docker 發行版的說明。如需下載不同於 `v0.25.0` 的 Docker 映像,請在執行 `docker compose` 啟動服務之前先更新 **docker/.env** 檔案內的 `RAGFLOW_IMAGE` 變數。 |
🧰 Tools
🪛 markdownlint-cli2 (0.22.0)
[warning] 194-194: Blank line inside blockquote
(MD028, no-blanks-blockquote)
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@README_tzh.md` around lines 194 - 196, The CAUTION blockquote in
README_tzh.md contains a blank line that triggers markdownlint MD028; fix it by
removing the empty line so the fenced code block directly follows the blockquote
text (e.g., ensure the line after "執行以下指令會自動下載 RAGFlow Docker 映像 `v0.25.0`..."
contains "```bash" immediately with no blank line), keep the language tag (bash)
on the opening fence and close the fence properly, and ensure there are no extra
blank lines inside that blockquote section so the blockquote lines are
contiguous.
| Where `{version_dir}` is the version with `.` replaced by `_`. | ||
|
|
||
| Example: Version `v0.24.0` → Directory `tools/migrate/v0_24_0/` | ||
| Example: Version `v0.25.0` → Directory `tools/migrate/v0_24_0/` |
There was a problem hiding this comment.
Fix incorrect version-directory mapping example.
Line 290 maps v0.25.0 to v0_24_0, which is incorrect. It should map to v0_25_0.
🛠️ Proposed fix
-Example: Version `v0.25.0` → Directory `tools/migrate/v0_24_0/`
+Example: Version `v0.25.0` → Directory `tools/migrate/v0_25_0/`📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Example: Version `v0.25.0` → Directory `tools/migrate/v0_24_0/` | |
| Example: Version `v0.25.0` → Directory `tools/migrate/v0_25_0/` |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@tools/scripts/README.md` at line 290, Update the example version-to-directory
mapping so the semantic version matches the directory suffix: change the mapping
text that currently shows "Version `v0.25.0` → Directory
`tools/migrate/v0_24_0/`" to use `tools/migrate/v0_25_0/` so the displayed
directory reflects the same patch number as the version string.
…iflow#14257) ### What problem does this PR solve? - Update version tags in README files (including translations) from v0.24.0 to v0.25.0 - Modify Docker image references and documentation to reflect new version - Update version badges and image descriptions - Maintain consistency across all language variants of README files ### Type of change - [x] Documentation Update
What problem does this PR solve?
Type of change